[jira] [Updated] (PARQUET-1014) Example for multiple row group writer (cpp)

["yugu (JIRA)" <ji...@apache.org>]

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

yugu updated PARQUET-1014:
--------------------------
       Priority: Major  (was: Minor)
    Description: 
Been looking through the repo and cannot find an example for multiple row group writer.

Probably missed that. Would be great if you guys can point it out ! : D

Thanks!

  was:
Error when trying to write multiple row groups and declare column writer (compile passes tho running into mem mapping issue)

I've been trying to do something like write several int/double columns, yet the second declaration of writer of the same type using next column crashes.

eg. say I have [int64.int64.int64,...double,double]

for (int __c = 0; __c < #columns; __c++)
{
    if (type == int64)
    {
        parquet::Int64Writer* int64_writer = static_cast<parquet::Int64Writer*>(rg_writer->NextColumn());
    }
    else if (type == double)
    {
        parquet::DoubleWriter *double_writer = static_cast<parquet::DoubleWriter *>(rg_writer->NextColumn());
    }
}

I've been looking through the examples in parquet-cpp repo but could not find a fix (or similar example).

     Issue Type: Improvement  (was: Bug)
        Summary: Example for multiple row group writer (cpp)  (was: Conflicts in declaring Column Writer of same type)

> Example for multiple row group writer (cpp)
> -------------------------------------------
>
>                 Key: PARQUET-1014
>                 URL: https://issues.apache.org/jira/browse/PARQUET-1014
>             Project: Parquet
>          Issue Type: Improvement
>          Components: parquet-cpp
>    Affects Versions: cpp-1.1.0
>            Reporter: yugu
>             Fix For: cpp-1.1.0
>
>
> Been looking through the repo and cannot find an example for multiple row group writer.
> Probably missed that. Would be great if you guys can point it out ! : D
> Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)