[
https://issues.apache.org/jira/browse/PHOENIX-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17275306#comment-17275306
]
ASF GitHub Bot commented on PHOENIX-6349:
-----------------------------------------
yanxinyi commented on a change in pull request #1122:
URL: https://github.com/apache/phoenix/pull/1122#discussion_r567073741
##########
File path: pom.xml
##########
@@ -82,7 +82,7 @@
<hadoop.version>3.1.4</hadoop.version>
<hbase.thirdparty.version>2.2.1</hbase.thirdparty.version>
- <phoenix.thirdparty.version>1.0.0</phoenix.thirdparty.version>
+ <phoenix.thirdparty.version>1.1.0-SNAPSHOT</phoenix.thirdparty.version>
Review comment:
we will replace the release version after the phoenix 3rd party release
right?
should we wait and then merge this?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
> Add and use commons-cli to phoenix-thirdparty
> ---------------------------------------------
>
> Key: PHOENIX-6349
> URL: https://issues.apache.org/jira/browse/PHOENIX-6349
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
>
> We are hit hard by commons-cli bugs, and currently we msut stick to the
> version used by HBase/Hadoop.
> Adding commons-cli to phoenix-thirdparty would unchain us from the
> Hbase/Hadoop version, and would let us add our own patches (modeled after
> protobuf in HBase)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
