# Arrow.write on NamedTuple

**URL:** <https://discourse.julialang.org/t/arrow-write-on-namedtuple/54538>\
**Category:** General Usage\
**Created:** [February 3, 2021, 2:32pm UTC](https://discourse.julialang.org/t/arrow-write-on-namedtuple/54538 "2021-02-03T14:32:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![atteson](https://avatars.discourse-cdn.com/v4/letter/a/91b2a8/32.png) [@atteson](https://discourse.julialang.org/u/atteson)\
**Post date:** [February 3, 2021, 2:32pm UTC](https://discourse.julialang.org/t/arrow-write-on-namedtuple/54538/1 "2021-02-03T14:32:19Z")

</div>

The Arrow.jl documentation seems to indicate that I can use Arrow.write on NamedTuple’s of AbstractVector’s. Can anyone help me understand why the following code doesn’t work:

```julia
using Arrow
Arrow.write( "test", (x=collect(1:10),) )

```

---

<div class="post-metadata">

**Author:** ![nilshg](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nilshg/32/2283_2.png) [@nilshg](https://discourse.julialang.org/u/nilshg)\
**Post date:** [February 3, 2021, 3:32pm UTC](https://discourse.julialang.org/t/arrow-write-on-namedtuple/54538/2 "2021-02-03T15:32:13Z")

</div>

Could you clarify what your problem is? I’m seeing this:

```julia
julia> using Arrow, DataFrames

julia> Arrow.write("test", (x = collect(1:10), ))
"test"

julia> DataFrame(Arrow.Table("test"))
10×1 DataFrame
 Row │ x     
     │ Int64 
─────┼───────
   1 │ 1
   2 │ 2
   3 │ 3
   4 │ 4
   5 │ 5
   6 │ 6
   7 │ 7
   8 │ 8
   9 │ 9
  10 │ 10

(jl_MUttpq) pkg> st
Status `C:\Users\ngudat\AppData\Local\Temp\jl_MUttpq\Project.toml`
  [69666777] Arrow v1.2.2

```

---

<div class="post-metadata">

**Author:** ![atteson](https://avatars.discourse-cdn.com/v4/letter/a/91b2a8/32.png) [@atteson](https://discourse.julialang.org/u/atteson)\
**Post date:** [February 3, 2021, 5:29pm UTC](https://discourse.julialang.org/t/arrow-write-on-namedtuple/54538/3 "2021-02-03T17:29:33Z")

</div>

Thanks for your response. The issue was that the package manager installed an old version of the package (0.2.4). Updating fixed it.