You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@orc.apache.org by "cedric (JIRA)" <ji...@apache.org> on 2019/03/06 08:39:00 UTC

[jira] [Updated] (ORC-474) ColumnVectorBatch would benefit from a clean() method to reset all numElements recusively

     [ https://issues.apache.org/jira/browse/ORC-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

cedric updated ORC-474:
-----------------------
    Description: 
When dealing with deeply nested structure it can be quite tedious to reset all numElements recursively after a batch has been written. In practice, the simplest is probably for the client to create his own classes inheriting all of ColumnVectorBatches classes and adding such a clear() method to reset all numElements recursively.

Shouldn't liborc just provide that?

  was:
When dealing with deeply nested structure it can be quite tedious to reset all numElements recursively after a batch has been written. In practice, the simplest is probably for the client to create his own classes inheriting all of ColumnVectorBatches classes and adding such a clean() method to reset all numElements recursively.

Shouldn't liborc just provide that?


> ColumnVectorBatch would benefit from a clean() method to reset all numElements recusively
> -----------------------------------------------------------------------------------------
>
>                 Key: ORC-474
>                 URL: https://issues.apache.org/jira/browse/ORC-474
>             Project: ORC
>          Issue Type: Wish
>          Components: C++
>            Reporter: cedric
>            Priority: Minor
>
> When dealing with deeply nested structure it can be quite tedious to reset all numElements recursively after a batch has been written. In practice, the simplest is probably for the client to create his own classes inheriting all of ColumnVectorBatches classes and adding such a clear() method to reset all numElements recursively.
> Shouldn't liborc just provide that?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)