You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@parquet.apache.org by "Zoltan Ivanfi (JIRA)" <ji...@apache.org> on 2018/02/22 09:32:00 UTC
[jira] [Comment Edited] (PARQUET-1234) Release Parquet format 2.5.0
[ https://issues.apache.org/jira/browse/PARQUET-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372577#comment-16372577 ]
Zoltan Ivanfi edited comment on PARQUET-1234 at 2/22/18 9:31 AM:
-----------------------------------------------------------------
[~rdblue], I suggest we decide this on the Parquet sync next week.
I hope PARQUET-1222 will not take that long to resolve as I already have a proposal in the JIRA description and I would like to create a PR early next week. Then we can discuss it in the Parquet sync and if everyone agrees to the proposal, we may resolve that issue by end of next week.
If, on the other hand, the community will raise problems, concerns, or new alternatives, the fix will take more time, and we may consider an earlier release as well. However, even if we don't introduce a new ordering in the next release, we should still clarify the specification by explicitly calling out this ambiguity and the countermeasures that have to be taken to deal with the consequences (basically the bullet points at the end of the description of PARQUET-1222). And I think this is a significant change in itself that may deserve a minor version change.
was (Author: zi):
[~rdblue], I suggest we decide this on the Parquet sync next week.
I hope PARQUET-1222 will not take that long to resolve as I already have a proposal in the JIRA description and I would like to create a PR early next week. Then we can discuss it in the Parquet sync and if everyone agrees to the proposal, we may resolve that issue by end of next week.
If, on the other hand, the community will raise problems, concerns, or new alternatives, the fix will take more time, and we may consider an earlier release as well. However, even if we don't introduce a new ordering in the next release, we should still clarify the specification by explicitly calling out this ambiguity and the countermeasures that have to be taken to deal with the consequences (basically the last bullet list in the description of PARQUET-1222). And I think this is a significant change in itself that may deserve a minor version change.
> Release Parquet format 2.5.0
> ----------------------------
>
> Key: PARQUET-1234
> URL: https://issues.apache.org/jira/browse/PARQUET-1234
> Project: Parquet
> Issue Type: Task
> Components: parquet-format
> Affects Versions: format-2.5.0
> Reporter: Gabor Szadovszky
> Priority: Major
> Fix For: format-2.5.0
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)