[ https://issues.apache.org/jira/browse/ARROW-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947126#comment-15947126 ]
Emilio Lahr-Vivaz edited comment on ARROW-725 at 3/29/17 1:31 PM: ------------------------------------------------------------------ Should I make that change as part of adding the list? Or leave it for now? edit: I think I'll leave it for now, as I'm not entirely comfortable with the C++ codebase yet. was (Author: elahrvivaz): Should I make that change as part of adding the list? Or leave it for now? > [Format] Constant length list type > ---------------------------------- > > Key: ARROW-725 > URL: https://issues.apache.org/jira/browse/ARROW-725 > Project: Apache Arrow > Issue Type: Improvement > Components: Format > Reporter: Brian Hulette > Assignee: Emilio Lahr-Vivaz > Priority: Trivial > > It makes sense to store some data in a row-based format. For example, a > position might be stored as two or three coordinates per row, and all of them > will almost always be accessed simultaneously. Currently, arrow must store > these as two or three separate vectors, but cache performance could > potentially be improved if every coordinate for a given row were in the same > location in memory. > The List type could satisfy this requirement, but it requires an additional > offset vector which isn't necessary when every element is the same size. I > think it would be helpful to define a new type that is essentially a List > with every element having the same length. I think "Tuple" would be a natural > fit for this type but I'm open to other suggestions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)