[ 
https://issues.apache.org/jira/browse/ARROW-7513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013120#comment-17013120
 ] 

Paul Taylor commented on ARROW-7513:
------------------------------------

[~lmeyerov] Int64Vector and Uint64Vector.from methods either require you pass 
the JS BigInt types, or a second "is64bit" boolean argument: 
https://github.com/apache/arrow/blob/master/js/src/vector/int.ts#L63-L64. All 
the IntVectors share the same from implementation IIRC because of a limitation 
in the typescript compiler that may not exist anymore.

> [JS] Arrow Tutorial: Common data types
> --------------------------------------
>
>                 Key: ARROW-7513
>                 URL: https://issues.apache.org/jira/browse/ARROW-7513
>             Project: Apache Arrow
>          Issue Type: Task
>          Components: JavaScript
>            Reporter: Leo Meyerovich
>            Assignee: Leo Meyerovich
>            Priority: Minor
>
> The JS client lacks basic introductory material around creating the common 
> basic data types such as turning JS arrays into ints, dicts, etc. There is no 
> equivalent of Python's [https://arrow.apache.org/docs/python/data.html] . 
> This has made use for myself difficult, and I bet for others.
>  
> As with prev tutorials, I started sketching on 
> [https://observablehq.com/@lmeyerov/rich-data-types-in-apache-arrow-js-efficient-data-tables-wit]
>   . When we're happy can make sense to export as an html or something to the 
> repo, or just link from the main readme.
> I believe the target topics worth covering are:
>  * Common user data types: Ints, Dicts, Struct, Time
>  * Common column types: Data, Vector, Column
>  * Going from individual & arrays & buffers of JS values to Arrow-wrapped 
> forms, and basic inspection of the result
> Not worth going into here is Tables vs. RecordBatches, which is the other 
> tutorial.
>  
> 1. Ideas of what to add/edit/remove?
> 2. And anyone up for helping with discussion of Data vs. Vector, and ingest 
> of Time & Struct?
> 3. ... Should we be encouraging Struct or Map? I saw some PRs changing stuff 
> here.
>  
> cc [~wesm] [~bhulette] [~paul.e.taylor]
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to