[GitHub] [arrow] emkornfield commented on pull request #7973: ARROW-8493: [C++][Parquet] Start populating repeated ancestor defintion

2020-08-25 Thread GitBox
emkornfield commented on pull request #7973: URL: https://github.com/apache/arrow/pull/7973#issuecomment-680594450 @pitrou does the updated PR look OK? This is an automated message from the Apache Git Service. To respond to

[GitHub] [arrow] emkornfield commented on pull request #7973: ARROW-8493: [C++][Parquet] Start populating repeated ancestor defintion

2020-08-19 Thread GitBox
emkornfield commented on pull request #7973: URL: https://github.com/apache/arrow/pull/7973#issuecomment-676927791 CC @wesm or @pitrou This is an automated message from the Apache Git Service. To respond to the message,

[GitHub] [arrow] emkornfield commented on pull request #7973: ARROW-8493: [C++][Parquet] Start populating repeated ancestor defintion

2020-08-18 Thread GitBox
emkornfield commented on pull request #7973: URL: https://github.com/apache/arrow/pull/7973#issuecomment-675585382 > Is it better to create an issue in PARQUET instead of ARROW? It is a fine line. Generally, I use PARQUET for issues related to core parquet reading (i.e. not arrow