Re: ARROW-1463: Subtask ARROW-1471 Requirements for Value Vector Updates

2017-10-01 Thread Siddharth Teotia
Thanks Li. I will wait for a day to receive any further comments before marking ARROW-1471 as resolved -- not to imply that requirements are set "in stone" and nothing can be changed. This is just to make sure we are making progress. Thanks, Siddharth On Sun, Oct 1, 2017 at 12:28 PM, Li Jin wro

Re: ARROW-1463: Subtask ARROW-1471 Requirements for Value Vector Updates

2017-10-01 Thread Li Jin
Siddharth, The requirement doc looks good to me. Thanks for putting this together. Li On Sun, Oct 1, 2017 at 1:20 PM, Siddharth Teotia wrote: > Hi All, > > I am assuming that there are no more requirements to be added/suggested. If > so, we can proceed with designing and prototyping as mention

Re: ARROW-1463: Subtask ARROW-1471 Requirements for Value Vector Updates

2017-10-01 Thread Siddharth Teotia
Hi All, I am assuming that there are no more requirements to be added/suggested. If so, we can proceed with designing and prototyping as mentioned in other subtasks. Recently we discovered requirement w.r.t heap usage in vector/memory code. So that is something that I need to note down in the req

Re: ARROW-1463: Subtask ARROW-1471 Requirements for Value Vector Updates

2017-09-21 Thread Bryan Cutler
Thanks for doing this Siddharth! The link in your email isn't clickable for me, so for us folks too lazy to cut and paste I'll try adding it again https://docs.google.com/document/d/1ysZ76zritBDwkeQz3C6-vhQwD32jEXd1kUF4T936G1U/edit On Thu, Sep 21, 2017 at 2:18 PM, Siddharth Teotia wrote: > Hi

ARROW-1463: Subtask ARROW-1471 Requirements for Value Vector Updates

2017-09-21 Thread Siddharth Teotia
Hi All, You should have received an invitation to edit the following document. Please feel free to add comments or additional content. https://docs.google.com/document/d/1ysZ76zritBDwkeQz3C6- vhQwD32jEXd1kUF4T936G1U/edit?usp=sharing Thanks, Siddharth