[
https://issues.apache.org/jira/browse/PARQUET-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17391453#comment-17391453
]
ASF GitHub Bot commented on PARQUET-2064:
-----------------------------------------
gszadovszky commented on pull request #918:
URL: https://github.com/apache/parquet-mr/pull/918#issuecomment-890851073
@shangxinli, when I've said we should move the class `RowRanges` from the
internal package I did not realize it would be a breaking change from java API
point of view. japicmp is right and it is not easy to suppress such errors. We
can exclude the whole rule or the related class from the check but it might
lead to uncaught changes in the future.
The easiest and more future proof solution is to leave the class `RowRanges`
in the internal package. (Sorry for the confusion.) It is not the best solution
because it might be misleading to the API clients but I don't have a better one.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@parquet.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Make Range public accessible in RowRanges
> -----------------------------------------
>
> Key: PARQUET-2064
> URL: https://issues.apache.org/jira/browse/PARQUET-2064
> Project: Parquet
> Issue Type: New Feature
> Reporter: Xinli Shang
> Assignee: Xinli Shang
> Priority: Major
>
> When rolling out to Presto, I found we need to know the boundaries of each
> Range in RowRanges. It is still doable with Iterator but Presto has. batch
> reader, we cannot use iterator for each row.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
