[jira] [Created] (OMID-189) Fix RAT check errors
Istvan Toth created OMID-189: Summary: Fix RAT check errors Key: OMID-189 URL: https://issues.apache.org/jira/browse/OMID-189 Project: Phoenix Omid Issue Type: Bug Affects Versions: 1.0.2 Reporter: Istvan Toth We have some RAT check errors in 1.0.2 as noticed by Josh and Rajeshbabu: > ``` > misc/findbugs-exclude.xml > misc/omid_checks.xml > bintray-settings.xml > doc/images/ModuleDependencies.graffle > doc/site/site.xml > .travis.yml > ``` Fix those -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OMID-187) Fix incorrect URL of source code
[ https://issues.apache.org/jira/browse/OMID-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth reassigned OMID-187: Assignee: Chia-Ping Tsai > Fix incorrect URL of source code > > > Key: OMID-187 > URL: https://issues.apache.org/jira/browse/OMID-187 > Project: Phoenix Omid > Issue Type: Bug >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Trivial > Fix For: 1.0.2 > > > https://git-wip-us.apache.org/repos/asf/incubator-omid.git is not available > and the replacement is > https://git-wip-us.apache.org/repos/asf/phoenix-omid.git -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OMID-155) disable trimStackTrace
[ https://issues.apache.org/jira/browse/OMID-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth reassigned OMID-155: Assignee: Istvan Toth > disable trimStackTrace > -- > > Key: OMID-155 > URL: https://issues.apache.org/jira/browse/OMID-155 > Project: Phoenix Omid > Issue Type: Improvement >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 1.0.2 > > Time Spent: 10m > Remaining Estimate: 0h > > I propose that we disable the trimStackTrace surefire/failsafe option. > See the identical PHOENIX-5814 for more information. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OMID-153) The method AbstractTransactionManager.closeResources should be protected instead of package private
[
https://issues.apache.org/jira/browse/OMID-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth reassigned OMID-153:
Assignee: (was: Istvan Toth)
> The method AbstractTransactionManager.closeResources should be protected
> instead of package private
> ---
>
> Key: OMID-153
> URL: https://issues.apache.org/jira/browse/OMID-153
> Project: Phoenix Omid
> Issue Type: Bug
>Affects Versions: 1.0.1
>Reporter: Robert Yokota
>Priority: Minor
> Fix For: 1.0.2
>
>
> I was trying to subclass {{AbstractTransactionManager}} from a class in
> another package, and I was not able to because the method {{closeResources}}
> is package private instead of protected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (OMID-153) The method AbstractTransactionManager.closeResources should be protected instead of package private
[
https://issues.apache.org/jira/browse/OMID-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth reassigned OMID-153:
Assignee: Istvan Toth
> The method AbstractTransactionManager.closeResources should be protected
> instead of package private
> ---
>
> Key: OMID-153
> URL: https://issues.apache.org/jira/browse/OMID-153
> Project: Phoenix Omid
> Issue Type: Bug
>Affects Versions: 1.0.1
>Reporter: Robert Yokota
>Assignee: Istvan Toth
>Priority: Minor
> Fix For: 1.0.2
>
>
> I was trying to subclass {{AbstractTransactionManager}} from a class in
> another package, and I was not able to because the method {{closeResources}}
> is package private instead of protected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (OMID-190) Update website for 1.0.2
Istvan Toth created OMID-190: Summary: Update website for 1.0.2 Key: OMID-190 URL: https://issues.apache.org/jira/browse/OMID-190 Project: Phoenix Omid Issue Type: Improvement Affects Versions: 1.0.2 Reporter: Istvan Toth Assignee: Istvan Toth The site repo URL has changed, and the download links point to the old repo and relase dirs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6231) Update Omid to 1.0.2
Istvan Toth created PHOENIX-6231: Summary: Update Omid to 1.0.2 Key: PHOENIX-6231 URL: https://issues.apache.org/jira/browse/PHOENIX-6231 Project: Phoenix Issue Type: Improvement Components: core Affects Versions: 5.0.0, 4.16.0 Reporter: Istvan Toth Assignee: Istvan Toth Update Omid to 1.0.2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6231) Update Omid to 1.0.2
[ https://issues.apache.org/jira/browse/PHOENIX-6231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-6231: - Description: Update Omid to 1.0.2 Note that while for master this is a simple update from -SNAPSHOT to final version, for 4.x this includes pulling in phoenix-thirdparty Guava, and the same minor code changes has master alterady hase. was:Update Omid to 1.0.2 > Update Omid to 1.0.2 > > > Key: PHOENIX-6231 > URL: https://issues.apache.org/jira/browse/PHOENIX-6231 > Project: Phoenix > Issue Type: Improvement > Components: core >Affects Versions: 5.0.0, 4.16.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > > Update Omid to 1.0.2 > Note that while for master this is a simple update from -SNAPSHOT to final > version, for 4.x this includes pulling in phoenix-thirdparty Guava, and the > same minor code changes has master alterady hase. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6231) Update Omid to 1.0.2
[ https://issues.apache.org/jira/browse/PHOENIX-6231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-6231: - Description: Update Omid to 1.0.2 Note that while for master this is a simple update from -SNAPSHOT to final version, for 4.x this includes pulling in phoenix-thirdparty Guava, and the same minor code change has master already has. was: Update Omid to 1.0.2 Note that while for master this is a simple update from -SNAPSHOT to final version, for 4.x this includes pulling in phoenix-thirdparty Guava, and the same minor code changes has master alterady hase. > Update Omid to 1.0.2 > > > Key: PHOENIX-6231 > URL: https://issues.apache.org/jira/browse/PHOENIX-6231 > Project: Phoenix > Issue Type: Improvement > Components: core >Affects Versions: 5.0.0, 4.16.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > > Update Omid to 1.0.2 > Note that while for master this is a simple update from -SNAPSHOT to final > version, for 4.x this includes pulling in phoenix-thirdparty Guava, and the > same minor code change has master already has. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OMID-190) Update website for 1.0.2
[ https://issues.apache.org/jira/browse/OMID-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved OMID-190. -- Fix Version/s: 1.0.3 Resolution: Fixed Thanks for the review [~chia7712]. > Update website for 1.0.2 > > > Key: OMID-190 > URL: https://issues.apache.org/jira/browse/OMID-190 > Project: Phoenix Omid > Issue Type: Improvement >Affects Versions: 1.0.2 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 1.0.3 > > > The site repo URL has changed, and the download links point to the old repo > and relase dirs. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (OMID-190) Update website for 1.0.2
[ https://issues.apache.org/jira/browse/OMID-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth reopened OMID-190: -- Reopening, as we still need to apply the changes to the live website. > Update website for 1.0.2 > > > Key: OMID-190 > URL: https://issues.apache.org/jira/browse/OMID-190 > Project: Phoenix Omid > Issue Type: Improvement >Affects Versions: 1.0.2 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 1.0.3 > > > The site repo URL has changed, and the download links point to the old repo > and relase dirs. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6231) Update Omid to 1.0.2
[ https://issues.apache.org/jira/browse/PHOENIX-6231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-6231. -- Fix Version/s: 4.16.0 5.1.0 Resolution: Fixed Committed to master and 4.x Thanks for the review [~vjasani]. > Update Omid to 1.0.2 > > > Key: PHOENIX-6231 > URL: https://issues.apache.org/jira/browse/PHOENIX-6231 > Project: Phoenix > Issue Type: Improvement > Components: core >Affects Versions: 5.0.0, 4.16.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 5.1.0, 4.16.0 > > > Update Omid to 1.0.2 > Note that while for master this is a simple update from -SNAPSHOT to final > version, for 4.x this includes pulling in phoenix-thirdparty Guava, and the > same minor code change has master already has. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6068) (5.x) Read repair reduces the number of rows returned for LIMIT queries
[ https://issues.apache.org/jira/browse/PHOENIX-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-6068. -- Resolution: Fixed This was resolved as part of the indexing rebase. The changes and the test are in master now, and the test passes. > (5.x) Read repair reduces the number of rows returned for LIMIT queries > --- > > Key: PHOENIX-6068 > URL: https://issues.apache.org/jira/browse/PHOENIX-6068 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.0.0, 4.14.3 >Reporter: Kadir OZDEMIR >Priority: Blocker > Fix For: 5.1.0 > > > Phoenix uses HBase PageFilter to limit the number of rows returned by scans. > If a scanned index row is unverified, GlobalIndexChecker repairs this rows. > This repair operation leads to either skipping the unverified row or scanning > its repaired version. Every scanned row including unverified rows are counted > by the page filter. Since unverified rows are counted but not returned for > the query, the actual number of rows returned for a LIMIT query becomes less > than the set limit (i.e., page size) for the query. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-4524) Remove Flume dependency from Phoenix-Kafka plugin
[ https://issues.apache.org/jira/browse/PHOENIX-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-4524: - Component/s: kafka-connector connectors Issue Type: Improvement (was: Bug) Priority: Major (was: Blocker) > Remove Flume dependency from Phoenix-Kafka plugin > - > > Key: PHOENIX-4524 > URL: https://issues.apache.org/jira/browse/PHOENIX-4524 > Project: Phoenix > Issue Type: Improvement > Components: connectors, kafka-connector >Affects Versions: 4.12.0 >Reporter: Artem Ervits >Priority: Major > > Phoenix Kafka plugin heavily depends on Phoenix Flume Plugin which in turn > depends on Apache Flume. This jira is proposed to remove Flume dependency > from Phoenix-Kafka plugin. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-4524) Remove Flume dependency from Phoenix-Kafka plugin
[ https://issues.apache.org/jira/browse/PHOENIX-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-4524: - Comment: was deleted (was: I agree that this would be beneficial, but I don't think that this is a bug, or a blocker.) > Remove Flume dependency from Phoenix-Kafka plugin > - > > Key: PHOENIX-4524 > URL: https://issues.apache.org/jira/browse/PHOENIX-4524 > Project: Phoenix > Issue Type: Improvement > Components: connectors, kafka-connector >Affects Versions: 4.12.0 >Reporter: Artem Ervits >Priority: Major > > Phoenix Kafka plugin heavily depends on Phoenix Flume Plugin which in turn > depends on Apache Flume. This jira is proposed to remove Flume dependency > from Phoenix-Kafka plugin. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TEPHRA-315) tephra-example maven setup is broken
[ https://issues.apache.org/jira/browse/TEPHRA-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238131#comment-17238131 ] Istvan Toth commented on TEPHRA-315: Thanks for the review Josh. > tephra-example maven setup is broken > > > Key: TEPHRA-315 > URL: https://issues.apache.org/jira/browse/TEPHRA-315 > Project: Phoenix Tephra > Issue Type: Bug >Affects Versions: 0.16.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Blocker > Fix For: 0.16.0, 0.17.0 > > > I could not deploy the 0.16.0RC0 because mvn deploy fails. > Unfortunately the mvn build fails only on the deploy target, it doesn't fail > on package or install. > The reason is that the example submodules are set up incorrectly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (TEPHRA-315) tephra-example maven setup is broken
[ https://issues.apache.org/jira/browse/TEPHRA-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved TEPHRA-315. Fix Version/s: 0.17.0 0.16.0 Resolution: Fixed Committed to master, and to to release/0.16.0 > tephra-example maven setup is broken > > > Key: TEPHRA-315 > URL: https://issues.apache.org/jira/browse/TEPHRA-315 > Project: Phoenix Tephra > Issue Type: Bug >Affects Versions: 0.16.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Blocker > Fix For: 0.16.0, 0.17.0 > > > I could not deploy the 0.16.0RC0 because mvn deploy fails. > Unfortunately the mvn build fails only on the deploy target, it doesn't fail > on package or install. > The reason is that the example submodules are set up incorrectly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OMID-190) Update website for 1.0.2
[ https://issues.apache.org/jira/browse/OMID-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238212#comment-17238212 ] Istvan Toth commented on OMID-190: -- I regenerated the site, and updated [https://github.com/apache/phoenix-omid-site] with it. Will check in a few hours if this had any effect on the live site. > Update website for 1.0.2 > > > Key: OMID-190 > URL: https://issues.apache.org/jira/browse/OMID-190 > Project: Phoenix Omid > Issue Type: Improvement >Affects Versions: 1.0.2 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 1.0.3 > > > The site repo URL has changed, and the download links point to the old repo > and relase dirs. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6233) QueryTimeoutIT fails sometimes.
[
https://issues.apache.org/jira/browse/PHOENIX-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-6233:
-
Issue Type: Bug (was: Task)
> QueryTimeoutIT fails sometimes.
> ---
>
> Key: PHOENIX-6233
> URL: https://issues.apache.org/jira/browse/PHOENIX-6233
> Project: Phoenix
> Issue Type: Bug
>Reporter: Richard Antal
>Assignee: Richard Antal
>Priority: Minor
> Attachments: PHOENIX-6233.4.x.v1.patch, PHOENIX-6233.master.v1.patch
>
>
> On a faster computers QueryTimeoutIT does not take 1000 ms.
> Sometimes on my computer it runs well below it. I suggest increasing nRows
> to make it stable for some year.
> One of my failing run (MacBook Pro 16 9th-gen i7):
> {code:java}
> QueryTimeoutIT.testQueryTimeout:134 Total time of query was 852 ms, but
> expected to be greater than 1000{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OMID-190) Update website for 1.0.2
[ https://issues.apache.org/jira/browse/OMID-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238573#comment-17238573 ] Istvan Toth commented on OMID-190: -- The live website isn't populated from that repo. Perhaps the website wasn't reconfigured to use the new repo when it changed ? Unless someone can shed light on this, the best idea seems to be contacting INFRA ? > Update website for 1.0.2 > > > Key: OMID-190 > URL: https://issues.apache.org/jira/browse/OMID-190 > Project: Phoenix Omid > Issue Type: Improvement >Affects Versions: 1.0.2 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 1.0.3 > > > The site repo URL has changed, and the download links point to the old repo > and relase dirs. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OMID-190) Update website for 1.0.2
[ https://issues.apache.org/jira/browse/OMID-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238574#comment-17238574 ] Istvan Toth commented on OMID-190: -- [~yonigo] As you seem to have made the last changes to website, can you advise on how we could restore our ability to update the website ? > Update website for 1.0.2 > > > Key: OMID-190 > URL: https://issues.apache.org/jira/browse/OMID-190 > Project: Phoenix Omid > Issue Type: Improvement >Affects Versions: 1.0.2 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 1.0.3 > > > The site repo URL has changed, and the download links point to the old repo > and relase dirs. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6234) Replace Guava with phoenix-thirdparty version in 4.x
Istvan Toth created PHOENIX-6234: Summary: Replace Guava with phoenix-thirdparty version in 4.x Key: PHOENIX-6234 URL: https://issues.apache.org/jira/browse/PHOENIX-6234 Project: Phoenix Issue Type: Improvement Components: core Affects Versions: 4.16.0 Reporter: Istvan Toth As discussed on the dev list, applying the Guava changes from PHOENIX-6010 on the 4.x branch would make our lives easier. 99% percent of the change is search-and-replace, the remaining 1% can probably be lifted from the master commit. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-4794) PhoenixStorageHandler broken with Hive 3.1
[ https://issues.apache.org/jira/browse/PHOENIX-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-4794. -- Resolution: Fixed The patch was included in PHOENIX-5786. Thank you [~jcamachorodriguez] . > PhoenixStorageHandler broken with Hive 3.1 > -- > > Key: PHOENIX-4794 > URL: https://issues.apache.org/jira/browse/PHOENIX-4794 > Project: Phoenix > Issue Type: Bug >Reporter: Josh Elser >Assignee: Jesus Camacho Rodriguez >Priority: Critical > Fix For: connectors-6.0.0 > > Attachments: PHOENIX-4794.001.patch > > > [~jcamachorodriguez] put together a nice patch on the heels of HIVE-12192 > (date/timestamp handling in Hive) which fixes Phoenix. Without this patch, > we'll see both compilation and runtime failures in the PhoenixStorageHandler > with Hive 3.1.0-SNAPSHOT. > Sadly, we need to wait for a Hive 3.1.0 to get this shipped in Phoenix. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-3662) PhoenixStorageHandler throws ClassCastException.
[
https://issues.apache.org/jira/browse/PHOENIX-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-3662:
-
Component/s: hive-connector
connectors
Fix Version/s: connectors-6.0.0
> PhoenixStorageHandler throws ClassCastException.
>
>
> Key: PHOENIX-3662
> URL: https://issues.apache.org/jira/browse/PHOENIX-3662
> Project: Phoenix
> Issue Type: Bug
> Components: connectors, hive-connector
>Affects Versions: 4.9.0
>Reporter: Jeongdae Kim
>Assignee: Jeongdae Kim
>Priority: Major
> Labels: HivePhoenix
> Fix For: connectors-6.0.0
>
> Attachments: PHOENIX-3662.1.patch, PHOENIX-3662.2.patch
>
>
> when executing a query that has between clauses embraced by function, phoenix
> storage handler throws class cast exception like below.
> and in addition, i found some bugs when handling push down predicates.
> {code}
> 2017-02-06T16:35:26,019 ERROR [7d29d400-2ec5-4ab8-84c2-041b55c3e24b
> HiveServer2-Handler-Pool: Thread-57]: ql.Driver
> (SessionState.java:printError(1097)) - FAILED: ClassCastException
> org.apache.hadoop.hive.ql.plan.ExprNodeGenericFuncDesc cannot be cast to
> org.apache.hadoop.hive.ql.plan.ExprNodeColumnDesc
> java.lang.ClassCastException:
> org.apache.hadoop.hive.ql.plan.ExprNodeGenericFuncDesc cannot be cast to
> org.apache.hadoop.hive.ql.plan.ExprNodeColumnDesc
> at
> org.apache.phoenix.hive.ql.index.IndexPredicateAnalyzer.processingBetweenOperator(IndexPredicateAnalyzer.java:229)
> at
> org.apache.phoenix.hive.ql.index.IndexPredicateAnalyzer.analyzeExpr(IndexPredicateAnalyzer.java:369)
> at
> org.apache.phoenix.hive.ql.index.IndexPredicateAnalyzer.access$000(IndexPredicateAnalyzer.java:72)
> at
> org.apache.phoenix.hive.ql.index.IndexPredicateAnalyzer$1.process(IndexPredicateAnalyzer.java:165)
> at
> org.apache.hadoop.hive.ql.lib.DefaultRuleDispatcher.dispatch(DefaultRuleDispatcher.java:90)
> at
> org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.dispatchAndReturn(DefaultGraphWalker.java:105)
> at
> org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.dispatch(DefaultGraphWalker.java:89)
> at
> org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.walk(DefaultGraphWalker.java:158)
> at
> org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.startWalking(DefaultGraphWalker.java:120)
> at
> org.apache.phoenix.hive.ql.index.IndexPredicateAnalyzer.analyzePredicate(IndexPredicateAnalyzer.java:176)
> at
> org.apache.phoenix.hive.ppd.PhoenixPredicateDecomposer.decomposePredicate(PhoenixPredicateDecomposer.java:63)
> at
> org.apache.phoenix.hive.PhoenixStorageHandler.decomposePredicate(PhoenixStorageHandler.java:238)
> at
> org.apache.hadoop.hive.ql.ppd.OpProcFactory.pushFilterToStorageHandler(OpProcFactory.java:1004)
> at
> org.apache.hadoop.hive.ql.ppd.OpProcFactory.createFilter(OpProcFactory.java:910)
> at
> org.apache.hadoop.hive.ql.ppd.OpProcFactory.createFilter(OpProcFactory.java:880)
> at
> org.apache.hadoop.hive.ql.ppd.OpProcFactory$TableScanPPD.process(OpProcFactory.java:429)
> at
> org.apache.hadoop.hive.ql.lib.DefaultRuleDispatcher.dispatch(DefaultRuleDispatcher.java:90)
> at
> org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.dispatchAndReturn(DefaultGraphWalker.java:105)
> at
> org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.dispatch(DefaultGraphWalker.java:89)
> at
> org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.walk(DefaultGraphWalker.java:158)
> at
> org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.startWalking(DefaultGraphWalker.java:120)
> at
> org.apache.hadoop.hive.ql.ppd.SimplePredicatePushDown.transform(SimplePredicatePushDown.java:102)
> at
> org.apache.hadoop.hive.ql.optimizer.Optimizer.optimize(Optimizer.java:242)
> at
> org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:10921)
> at
> org.apache.hadoop.hive.ql.parse.CalcitePlanner.analyzeInternal(CalcitePlanner.java:246)
> at
> org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:250)
> at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:471)
> at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:1242)
> at org.apache.hadoop.hive.ql.Driver.compileAndRespond(Driver.java:1229)
> at
> org.apache.hive.service.cli.operation.SQLOperation.prepare(SQLOperation.java:191)
> at
> org.apache.hive.service.cli.operation.SQLOperation.runInternal(SQLOperation.java:276)
> at
> org.apache.hive.service.cli.operation.Operation.run(Operation.java:324)
> at
> org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementInternal(HiveSessionImpl.ja
[jira] [Updated] (PHOENIX-4794) PhoenixStorageHandler broken with Hive 3.1
[ https://issues.apache.org/jira/browse/PHOENIX-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-4794: - Component/s: hive-connector connectors > PhoenixStorageHandler broken with Hive 3.1 > -- > > Key: PHOENIX-4794 > URL: https://issues.apache.org/jira/browse/PHOENIX-4794 > Project: Phoenix > Issue Type: Bug > Components: connectors, hive-connector >Reporter: Josh Elser >Assignee: Jesus Camacho Rodriguez >Priority: Critical > Fix For: connectors-6.0.0 > > Attachments: PHOENIX-4794.001.patch > > > [~jcamachorodriguez] put together a nice patch on the heels of HIVE-12192 > (date/timestamp handling in Hive) which fixes Phoenix. Without this patch, > we'll see both compilation and runtime failures in the PhoenixStorageHandler > with Hive 3.1.0-SNAPSHOT. > Sadly, we need to wait for a Hive 3.1.0 to get this shipped in Phoenix. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-4412) Tephra transaction context visibility level returns null instead of SNAPSHOT_ALL
[
https://issues.apache.org/jira/browse/PHOENIX-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth reassigned PHOENIX-4412:
Assignee: Istvan Toth
> Tephra transaction context visibility level returns null instead of
> SNAPSHOT_ALL
>
>
> Key: PHOENIX-4412
> URL: https://issues.apache.org/jira/browse/PHOENIX-4412
> Project: Phoenix
> Issue Type: Bug
>Reporter: Radivoje
>Assignee: Istvan Toth
>Priority: Critical
>
> This is on master branch but probably other versions are affected.
> The problem is in TephraTransactionContext
> {code:java}
> case SNAPSHOT_ALL:
> phoenixVisibilityLevel = PhoenixVisibilityLevel.SNAPSHOT_ALL;
> default:
> phoenixVisibilityLevel = null;
> }
> {code}
> break; is missing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6234) Replace Guava with phoenix-thirdparty version in 4.x
[ https://issues.apache.org/jira/browse/PHOENIX-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth reassigned PHOENIX-6234: Assignee: Istvan Toth > Replace Guava with phoenix-thirdparty version in 4.x > > > Key: PHOENIX-6234 > URL: https://issues.apache.org/jira/browse/PHOENIX-6234 > Project: Phoenix > Issue Type: Improvement > Components: core >Affects Versions: 4.16.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > > As discussed on the dev list, applying the Guava changes from PHOENIX-6010 on > the 4.x branch would make our lives easier. > 99% percent of the change is search-and-replace, the remaining 1% can > probably be lifted from the master commit. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6181) IndexRepairRegionScanner to verify and repair every global index row
[ https://issues.apache.org/jira/browse/PHOENIX-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-6181: - Fix Version/s: 5.1.0 > IndexRepairRegionScanner to verify and repair every global index row > > > Key: PHOENIX-6181 > URL: https://issues.apache.org/jira/browse/PHOENIX-6181 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.14.3 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-6181-Addendum.4.x.001.patch, > PHOENIX-6181.4.x.001.patch, PHOENIX-6181.4.x.002.patch, > PHOENIX-6181.master.001.patch, PHOENIX-6181.master.002.patch > > > IndexRebuildRegionScanner is the server side engine to rebuild and verify > every index row pointed by the data table. IndexRebuildRegionScanner runs on > data table regions and scans every data table rows locally, and then rebuilds > and verifies index table rows referenced by the data table rows over > server-to-server RPCs using the HBase client installed on region servers. > However, IndexRebuildRegionScanner cannot clean up the index rows that are > not referenced by the data table if there are such index rows. In order to do > that we need another region scanner that scans index table regions and makes > sure that every index row is valid. This region scanner will be called > IndexRepairRegionScanner. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-4412) Tephra transaction context visibility level returns null instead of SNAPSHOT_ALL
[
https://issues.apache.org/jira/browse/PHOENIX-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth resolved PHOENIX-4412.
--
Fix Version/s: 4.16.0
5.1.0
Resolution: Fixed
Committed to master and 4.x
Thanks for the review [~vjasani]
> Tephra transaction context visibility level returns null instead of
> SNAPSHOT_ALL
>
>
> Key: PHOENIX-4412
> URL: https://issues.apache.org/jira/browse/PHOENIX-4412
> Project: Phoenix
> Issue Type: Bug
>Reporter: Radivoje
>Assignee: Istvan Toth
>Priority: Critical
> Fix For: 5.1.0, 4.16.0
>
>
> This is on master branch but probably other versions are affected.
> The problem is in TephraTransactionContext
> {code:java}
> case SNAPSHOT_ALL:
> phoenixVisibilityLevel = PhoenixVisibilityLevel.SNAPSHOT_ALL;
> default:
> phoenixVisibilityLevel = null;
> }
> {code}
> break; is missing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6180) Investigate flaky tests in Phoenix Connectors
[ https://issues.apache.org/jira/browse/PHOENIX-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-6180. -- Resolution: Fixed Committed. Thanks for the review [~RichardAntal] > Investigate flaky tests in Phoenix Connectors > - > > Key: PHOENIX-6180 > URL: https://issues.apache.org/jira/browse/PHOENIX-6180 > Project: Phoenix > Issue Type: Task > Components: connectors >Affects Versions: connectors-6.0.0 >Reporter: Richard Antal >Assignee: Istvan Toth >Priority: Major > Fix For: connectors-6.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OMID-190) Update website for 1.0.2
[ https://issues.apache.org/jira/browse/OMID-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239099#comment-17239099 ] Istvan Toth commented on OMID-190: -- Thank you. > Update website for 1.0.2 > > > Key: OMID-190 > URL: https://issues.apache.org/jira/browse/OMID-190 > Project: Phoenix Omid > Issue Type: Improvement >Affects Versions: 1.0.2 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 1.0.3 > > > The site repo URL has changed, and the download links point to the old repo > and relase dirs. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6236) Document Stringly Consistent Global Indexes on website
Istvan Toth created PHOENIX-6236: Summary: Document Stringly Consistent Global Indexes on website Key: PHOENIX-6236 URL: https://issues.apache.org/jira/browse/PHOENIX-6236 Project: Phoenix Issue Type: Improvement Reporter: Istvan Toth Assignee: Istvan Toth Document Strongly Consistent Local Indexing, and the update procedure on the website -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6236) Document Strongly Consistent Global Indexes on website
[ https://issues.apache.org/jira/browse/PHOENIX-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-6236: - Summary: Document Strongly Consistent Global Indexes on website (was: Document Stringly Consistent Global Indexes on website) > Document Strongly Consistent Global Indexes on website > -- > > Key: PHOENIX-6236 > URL: https://issues.apache.org/jira/browse/PHOENIX-6236 > Project: Phoenix > Issue Type: Improvement >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Attachments: PHOENIX-6236.website.patch > > > Document Strongly Consistent Local Indexing, and the update procedure on the > website -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6234) Replace Guava with phoenix-thirdparty version in 4.x
[ https://issues.apache.org/jira/browse/PHOENIX-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth reassigned PHOENIX-6234: Assignee: (was: Istvan Toth) > Replace Guava with phoenix-thirdparty version in 4.x > > > Key: PHOENIX-6234 > URL: https://issues.apache.org/jira/browse/PHOENIX-6234 > Project: Phoenix > Issue Type: Improvement > Components: core >Affects Versions: 4.16.0 >Reporter: Istvan Toth >Priority: Major > > As discussed on the dev list, applying the Guava changes from PHOENIX-6010 on > the 4.x branch would make our lives easier. > 99% percent of the change is search-and-replace, the remaining 1% can > probably be lifted from the master commit. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6223) could not find or load main class sqline.SqLine
[ https://issues.apache.org/jira/browse/PHOENIX-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth reassigned PHOENIX-6223: Assignee: litianmei > could not find or load main class sqline.SqLine > --- > > Key: PHOENIX-6223 > URL: https://issues.apache.org/jira/browse/PHOENIX-6223 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.1.0 >Reporter: litianmei >Assignee: litianmei >Priority: Minor > Attachments: 0001-PHOENIX-6223.patch > > > when executing sqline.py for hbase, I receive this error: > Error: Could not find or load main class sqline.SqlLine > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6223) could not find or load main class sqline.SqLine
[ https://issues.apache.org/jira/browse/PHOENIX-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-6223. -- Fix Version/s: 4.16.0 5.1.0 Resolution: Fixed Committed to master and 4.x Thanks for the patch [~tianmei] . > could not find or load main class sqline.SqLine > --- > > Key: PHOENIX-6223 > URL: https://issues.apache.org/jira/browse/PHOENIX-6223 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.1.0 >Reporter: litianmei >Assignee: litianmei >Priority: Minor > Fix For: 5.1.0, 4.16.0 > > Attachments: 0001-PHOENIX-6223.patch > > > when executing sqline.py for hbase, I receive this error: > Error: Could not find or load main class sqline.SqlLine > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6223) could not find or load main class sqline.SqLine
[ https://issues.apache.org/jira/browse/PHOENIX-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth reassigned PHOENIX-6223: Assignee: litianmei (was: litianmei) > could not find or load main class sqline.SqLine > --- > > Key: PHOENIX-6223 > URL: https://issues.apache.org/jira/browse/PHOENIX-6223 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.1.0 >Reporter: litianmei >Assignee: litianmei >Priority: Minor > Attachments: 0001-PHOENIX-6223.patch > > > when executing sqline.py for hbase, I receive this error: > Error: Could not find or load main class sqline.SqlLine > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6237) Relocate javax. classes in phoenix-client
Istvan Toth created PHOENIX-6237: Summary: Relocate javax. classes in phoenix-client Key: PHOENIX-6237 URL: https://issues.apache.org/jira/browse/PHOENIX-6237 Project: Phoenix Issue Type: Improvement Components: core Affects Versions: 5.1.0, 4.16.0 Reporter: Istvan Toth Assignee: Istvan Toth We have the following unrelocated packages in phoenix-client: * javax.annotation * javax.inject * javax.validation * javax.xml We have seen at least javax.validation causing problems in activation. Investigate if any of these need to be unrelocated for the JDBC functionality, and relocate what we can. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6237) Relocate javax. classes in phoenix-client
[ https://issues.apache.org/jira/browse/PHOENIX-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-6237: - Description: We have the following unrelocated packages in phoenix-client: * javax.annotation * javax.inject * javax.validation * javax.xml We have seen at least javax.validation causing problems for applications. Investigate if any of these need to be unrelocated for the JDBC functionality, and relocate what we can. was: We have the following unrelocated packages in phoenix-client: * javax.annotation * javax.inject * javax.validation * javax.xml We have seen at least javax.validation causing problems in activation. Investigate if any of these need to be unrelocated for the JDBC functionality, and relocate what we can. > Relocate javax. classes in phoenix-client > - > > Key: PHOENIX-6237 > URL: https://issues.apache.org/jira/browse/PHOENIX-6237 > Project: Phoenix > Issue Type: Improvement > Components: core >Affects Versions: 5.1.0, 4.16.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > > We have the following unrelocated packages in phoenix-client: > * javax.annotation > * javax.inject > * javax.validation > * javax.xml > We have seen at least javax.validation causing problems for applications. > Investigate if any of these need to be unrelocated for the JDBC > functionality, and relocate what we can. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6236) Document Strongly Consistent Global Indexes on website
[ https://issues.apache.org/jira/browse/PHOENIX-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-6236: - Attachment: secondary_indexing.html > Document Strongly Consistent Global Indexes on website > -- > > Key: PHOENIX-6236 > URL: https://issues.apache.org/jira/browse/PHOENIX-6236 > Project: Phoenix > Issue Type: Improvement >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Attachments: PHOENIX-6236.website.patch, secondary_indexing.html > > > Document Strongly Consistent Local Indexing, and the update procedure on the > website -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6236) Document Strongly Consistent Global Indexes on website
[ https://issues.apache.org/jira/browse/PHOENIX-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-6236: - Attachment: Secondary_Indexing_current.htm > Document Strongly Consistent Global Indexes on website > -- > > Key: PHOENIX-6236 > URL: https://issues.apache.org/jira/browse/PHOENIX-6236 > Project: Phoenix > Issue Type: Improvement >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Attachments: PHOENIX-6236.website.patch, > Secondary_Indexing_current.htm, secondary_indexing.html > > > Document Strongly Consistent Local Indexing, and the update procedure on the > website -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6237) Relocate javax. classes in phoenix-client
[ https://issues.apache.org/jira/browse/PHOENIX-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-6237. -- Fix Version/s: 4.16.0 5.1.0 Resolution: Fixed Committed to master and 4.x Thanks for the review [~elserj] > Relocate javax. classes in phoenix-client > - > > Key: PHOENIX-6237 > URL: https://issues.apache.org/jira/browse/PHOENIX-6237 > Project: Phoenix > Issue Type: Improvement > Components: core >Affects Versions: 5.1.0, 4.16.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 5.1.0, 4.16.0 > > > We have the following unrelocated packages in phoenix-client: > * javax.annotation > * javax.inject > * javax.validation > * javax.xml > We have seen at least javax.validation causing problems for applications. > Investigate if any of these need to be unrelocated for the JDBC > functionality, and relocate what we can. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OMID-191) Fix missing executable permission because of MASSEMBLY-941
[ https://issues.apache.org/jira/browse/OMID-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated OMID-191: - Priority: Blocker (was: Major) > Fix missing executable permission because of MASSEMBLY-941 > -- > > Key: OMID-191 > URL: https://issues.apache.org/jira/browse/OMID-191 > Project: Phoenix Omid > Issue Type: Bug >Reporter: Richard Antal >Priority: Blocker > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OMID-191) Fix missing executable permission because of MASSEMBLY-941
[ https://issues.apache.org/jira/browse/OMID-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved OMID-191. -- Fix Version/s: 1.0.3 Resolution: Fixed Committed. Thanks for the fix [~RichardAntal] > Fix missing executable permission because of MASSEMBLY-941 > -- > > Key: OMID-191 > URL: https://issues.apache.org/jira/browse/OMID-191 > Project: Phoenix Omid > Issue Type: Bug >Reporter: Richard Antal >Priority: Blocker > Fix For: 1.0.3 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OMID-191) Fix missing executable permission because of MASSEMBLY-941
[ https://issues.apache.org/jira/browse/OMID-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth reassigned OMID-191: Assignee: Richard Antal > Fix missing executable permission because of MASSEMBLY-941 > -- > > Key: OMID-191 > URL: https://issues.apache.org/jira/browse/OMID-191 > Project: Phoenix Omid > Issue Type: Bug >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Blocker > Fix For: 1.0.3 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6238) Fix missing executable permission because of MASSEMBLY-941
[ https://issues.apache.org/jira/browse/PHOENIX-6238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-6238. -- Fix Version/s: queryserver-6.0.0 connectors-6.0.0 Resolution: Fixed Thank you [~RichardAntal] Committed to both -connectors and -queryserver with some changes. > Fix missing executable permission because of MASSEMBLY-941 > -- > > Key: PHOENIX-6238 > URL: https://issues.apache.org/jira/browse/PHOENIX-6238 > Project: Phoenix > Issue Type: Bug > Components: connectors, queryserver >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > Fix For: connectors-6.0.0, queryserver-6.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6240) Standardize connectors logging on SLF4j
Istvan Toth created PHOENIX-6240: Summary: Standardize connectors logging on SLF4j Key: PHOENIX-6240 URL: https://issues.apache.org/jira/browse/PHOENIX-6240 Project: Phoenix Issue Type: Improvement Components: connectors Affects Versions: connectors-6.0.0 Reporter: Istvan Toth Assignee: Istvan Toth We have already standardized on SLF4j in the other projects, finish this in connectors. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (TEPHRA-316) Fix missing executable permission because of MASSEMBLY-941
[ https://issues.apache.org/jira/browse/TEPHRA-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth reassigned TEPHRA-316: -- Assignee: Richard Antal (was: Poorna Chandra) > Fix missing executable permission because of MASSEMBLY-941 > -- > > Key: TEPHRA-316 > URL: https://issues.apache.org/jira/browse/TEPHRA-316 > Project: Phoenix Tephra > Issue Type: Bug >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6240) Standardize connectors logging on SLF4j
[ https://issues.apache.org/jira/browse/PHOENIX-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-6240. -- Fix Version/s: connectors-6.0.0 Resolution: Fixed Committed. Thanks for the quick review [~elserj]. > Standardize connectors logging on SLF4j > > > Key: PHOENIX-6240 > URL: https://issues.apache.org/jira/browse/PHOENIX-6240 > Project: Phoenix > Issue Type: Improvement > Components: connectors >Affects Versions: connectors-6.0.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: connectors-6.0.0 > > > We have already standardized on SLF4j in the other projects, finish this in > connectors. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6242) Remove remaining commons-logging references
Istvan Toth created PHOENIX-6242: Summary: Remove remaining commons-logging references Key: PHOENIX-6242 URL: https://issues.apache.org/jira/browse/PHOENIX-6242 Project: Phoenix Issue Type: Improvement Components: core Reporter: Istvan Toth We've largely finished the migration to slf4j, but 4.x has a few instances left, and the poms still reference it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6242) Remove remaining commons-logging references
[ https://issues.apache.org/jira/browse/PHOENIX-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth reassigned PHOENIX-6242: Assignee: Istvan Toth > Remove remaining commons-logging references > > > Key: PHOENIX-6242 > URL: https://issues.apache.org/jira/browse/PHOENIX-6242 > Project: Phoenix > Issue Type: Improvement > Components: core >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Minor > > We've largely finished the migration to slf4j, but 4.x has a few instances > left, and the poms still reference it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (TEPHRA-313) Remove support for ancient HBase releases
[ https://issues.apache.org/jira/browse/TEPHRA-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated TEPHRA-313: --- Fix Version/s: (was: 0.16) 0.16.0 > Remove support for ancient HBase releases > - > > Key: TEPHRA-313 > URL: https://issues.apache.org/jira/browse/TEPHRA-313 > Project: Phoenix Tephra > Issue Type: Improvement >Affects Versions: 0.16.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 0.16.0 > > > Tephra supports positively ancient HBase versions, that are unlikely to be > relevant by now. > Choose a cutoff point, and remove support for all versions older than that. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (TEPHRA-313) Remove support for ancient HBase releases
[ https://issues.apache.org/jira/browse/TEPHRA-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth reopened TEPHRA-313: > Remove support for ancient HBase releases > - > > Key: TEPHRA-313 > URL: https://issues.apache.org/jira/browse/TEPHRA-313 > Project: Phoenix Tephra > Issue Type: Improvement >Affects Versions: 0.16.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 0.16 > > > Tephra supports positively ancient HBase versions, that are unlikely to be > relevant by now. > Choose a cutoff point, and remove support for all versions older than that. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (TEPHRA-313) Remove support for ancient HBase releases
[ https://issues.apache.org/jira/browse/TEPHRA-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved TEPHRA-313. Resolution: Fixed Fixed fix version > Remove support for ancient HBase releases > - > > Key: TEPHRA-313 > URL: https://issues.apache.org/jira/browse/TEPHRA-313 > Project: Phoenix Tephra > Issue Type: Improvement >Affects Versions: 0.16.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 0.16.0 > > > Tephra supports positively ancient HBase versions, that are unlikely to be > relevant by now. > Choose a cutoff point, and remove support for all versions older than that. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (TEPHRA-313) Remove support for ancient HBase releases
[ https://issues.apache.org/jira/browse/TEPHRA-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth closed TEPHRA-313. -- > Remove support for ancient HBase releases > - > > Key: TEPHRA-313 > URL: https://issues.apache.org/jira/browse/TEPHRA-313 > Project: Phoenix Tephra > Issue Type: Improvement >Affects Versions: 0.16.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 0.16.0 > > > Tephra supports positively ancient HBase versions, that are unlikely to be > relevant by now. > Choose a cutoff point, and remove support for all versions older than that. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (TEPHRA-265) Tephra Guice License
[ https://issues.apache.org/jira/browse/TEPHRA-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated TEPHRA-265: --- Fix Version/s: (was: 0.16.0) 0.17.0 > Tephra Guice License > > > Key: TEPHRA-265 > URL: https://issues.apache.org/jira/browse/TEPHRA-265 > Project: Phoenix Tephra > Issue Type: Bug >Affects Versions: 0.13.0-incubating >Reporter: Gokul Gunasekaran >Assignee: Gokul Gunasekaran >Priority: Major > Fix For: 0.17.0 > > > The NOTICE for Guice in 0.13.0-incubating release contains (which was added > as part of the fix for TEPHRA-231): > Apache Tephra includes Guice v3.0 and Guice Assisted Inject v3.0. Tephra > elects to include this software in this distribution under the Apache License. > You can obtain a copy of the License at: > http://apache.org/licenses/LICENSE-2.0 > Instead, it should contain the exact content from the NOTICE of the Guice > JAR. > Google Guice - Core Library > Copyright 2006-2011 Google, Inc. > This product includes software developed at > The Apache Software Foundation (http://www.apache.org/). > http://mail-archives.apache.org/mod_mbox/incubator-general/201709.mbox/%3CCAOqetn-zPeOanD1fVZHVsjfwqn5qnmN9WXWjb1jDJAE8JgQ_Zg%40mail.gmail.com%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (TEPHRA-269) Protect the Transaction Manager against misconfigured clients using rate limits
[ https://issues.apache.org/jira/browse/TEPHRA-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated TEPHRA-269: --- Fix Version/s: (was: 0.16.0) 0.17.0 > Protect the Transaction Manager against misconfigured clients using rate > limits > --- > > Key: TEPHRA-269 > URL: https://issues.apache.org/jira/browse/TEPHRA-269 > Project: Phoenix Tephra > Issue Type: New Feature > Components: core >Reporter: Poorna Chandra >Assignee: Poorna Chandra >Priority: Major > Fix For: 0.17.0 > > Attachments: Ensure QoS in Transaction Manager by rate limiting > client requests.pdf > > > We have seen cases where misconfigured clients can overwhelm the system by > making expensive requests (like invalidating transactions). By the time > admins figure out there is a misconfigured client and take corrective action, > thousands of invalid transactions can be created in a very short period of > time. It would be useful to have a way to limit the number of invalid > transactions that a client can create in given time. > I'll send out a design document for this soon. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (TEPHRA-264) When transaction size limits are exceeded, the error message should indicate what configuration to change in order to increase the limit
[ https://issues.apache.org/jira/browse/TEPHRA-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated TEPHRA-264: --- Fix Version/s: (was: 0.16.0) 0.17.0 > When transaction size limits are exceeded, the error message should indicate > what configuration to change in order to increase the limit > > > Key: TEPHRA-264 > URL: https://issues.apache.org/jira/browse/TEPHRA-264 > Project: Phoenix Tephra > Issue Type: Improvement > Components: core >Affects Versions: 0.13.0-incubating >Reporter: Andreas Neumann >Assignee: Andreas Neumann >Priority: Major > Fix For: 0.17.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (TEPHRA-204) Document invalid transaction list pruning
[ https://issues.apache.org/jira/browse/TEPHRA-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated TEPHRA-204: --- Fix Version/s: (was: 0.16.0) 0.17.0 > Document invalid transaction list pruning > - > > Key: TEPHRA-204 > URL: https://issues.apache.org/jira/browse/TEPHRA-204 > Project: Phoenix Tephra > Issue Type: Sub-task >Reporter: Poorna Chandra >Assignee: Poorna Chandra >Priority: Major > Fix For: 0.17.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (TEPHRA-296) Prevent tephra-distribution from being included in source release
[ https://issues.apache.org/jira/browse/TEPHRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated TEPHRA-296: --- Fix Version/s: (was: 0.16.0) 0.17.0 > Prevent tephra-distribution from being included in source release > - > > Key: TEPHRA-296 > URL: https://issues.apache.org/jira/browse/TEPHRA-296 > Project: Phoenix Tephra > Issue Type: Improvement >Reporter: James R. Taylor >Assignee: Poorna Chandra >Priority: Blocker > Fix For: 0.17.0 > > Attachments: TEPHRA-296.patch > > > Since Tephra is only doing a source release, there's no need to include > anything inside of the tephra-distribution directory in the release tar ball. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6242) Remove remaining commons-logging references
[ https://issues.apache.org/jira/browse/PHOENIX-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-6242. -- Fix Version/s: 4.16.0 5.1.0 Resolution: Fixed Committed to master and 4.x. Thanks for the review [~vjasani] [~gjacoby] [~rajeshbabu]. > Remove remaining commons-logging references > > > Key: PHOENIX-6242 > URL: https://issues.apache.org/jira/browse/PHOENIX-6242 > Project: Phoenix > Issue Type: Improvement > Components: core >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Minor > Fix For: 5.1.0, 4.16.0 > > > We've largely finished the migration to slf4j, but 4.x has a few instances > left, and the poms still reference it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6245) Update tephra dependency version to 0.16.0
Istvan Toth created PHOENIX-6245: Summary: Update tephra dependency version to 0.16.0 Key: PHOENIX-6245 URL: https://issues.apache.org/jira/browse/PHOENIX-6245 Project: Phoenix Issue Type: Improvement Components: core Affects Versions: 5.1.0, 4.16.0 Reporter: Istvan Toth Assignee: Istvan Toth -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6245) Update tephra dependency version to 0.16.0
[ https://issues.apache.org/jira/browse/PHOENIX-6245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-6245: - Description: For master this mostly a cleanup, as the SNAPSHOT that we were using had already basically the same code. For 4.x this is a meaningful update, with real fixes and enabling Tephra support for HBase 1.5 and 1.6. > Update tephra dependency version to 0.16.0 > -- > > Key: PHOENIX-6245 > URL: https://issues.apache.org/jira/browse/PHOENIX-6245 > Project: Phoenix > Issue Type: Improvement > Components: core >Affects Versions: 5.1.0, 4.16.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > > For master this mostly a cleanup, as the SNAPSHOT that we were using had > already basically the same code. > For 4.x this is a meaningful update, with real fixes and enabling Tephra > support for HBase 1.5 and 1.6. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6236) Document Strongly Consistent Global Indexes on website
[ https://issues.apache.org/jira/browse/PHOENIX-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-6236: - Attachment: PHOENIX-6236.website.02.patch > Document Strongly Consistent Global Indexes on website > -- > > Key: PHOENIX-6236 > URL: https://issues.apache.org/jira/browse/PHOENIX-6236 > Project: Phoenix > Issue Type: Improvement >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Attachments: PHOENIX-6236.website.02.patch, > PHOENIX-6236.website.patch, Secondary_Indexing_current.htm, > secondary_indexing.html > > > Document Strongly Consistent Local Indexing, and the update procedure on the > website -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6236) Document Strongly Consistent Global Indexes on website
[ https://issues.apache.org/jira/browse/PHOENIX-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-6236: - Attachment: secondary_indexing.html > Document Strongly Consistent Global Indexes on website > -- > > Key: PHOENIX-6236 > URL: https://issues.apache.org/jira/browse/PHOENIX-6236 > Project: Phoenix > Issue Type: Improvement >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Attachments: PHOENIX-6236.website.02.patch, > PHOENIX-6236.website.patch, Secondary_Indexing_current.htm, > secondary_indexing.html, secondary_indexing.html > > > Document Strongly Consistent Local Indexing, and the update procedure on the > website -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6236) Document Strongly Consistent Global Indexes on website
[ https://issues.apache.org/jira/browse/PHOENIX-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-6236: - Attachment: (was: secondary_indexing.html) > Document Strongly Consistent Global Indexes on website > -- > > Key: PHOENIX-6236 > URL: https://issues.apache.org/jira/browse/PHOENIX-6236 > Project: Phoenix > Issue Type: Improvement >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Attachments: PHOENIX-6236.website.02.patch, > PHOENIX-6236.website.patch, Secondary_Indexing_current.htm, > secondary_indexing.html > > > Document Strongly Consistent Local Indexing, and the update procedure on the > website -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OMID-192) fix missing jcommander dependency
[
https://issues.apache.org/jira/browse/OMID-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth reassigned OMID-192:
Assignee: Istvan Toth
> fix missing jcommander dependency
> -
>
> Key: OMID-192
> URL: https://issues.apache.org/jira/browse/OMID-192
> Project: Phoenix Omid
> Issue Type: Bug
>Reporter: Richard Antal
>Assignee: Istvan Toth
>Priority: Major
>
> When I started the the **_omid.sh create-hbase-commit-table
> _I got the following exception:
> {{}}
> {code:java}
> Error: A JNI error has occurred, please check your installation and try again
> Exception in thread "main" java.lang.NoClassDefFoundError:
> com/beust/jcommander/ParameterException{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OMID-192) fix missing jcommander dependency
[
https://issues.apache.org/jira/browse/OMID-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243965#comment-17243965
]
Istvan Toth commented on OMID-192:
--
This is caused by upgrading maven-assembly-module, where the new version does
something differently, based on the scope of the included dependent module.
The real problem is the that Omid mixes code and assemblies in the same
subproject, which makes it impossible to define the dependencies properly.
My proposed fix changes the dependency to runtime, which is rather arbitrary,
but this one seems to be the scope that impacts the code the least, while
fixing the assembly contents.
> fix missing jcommander dependency
> -
>
> Key: OMID-192
> URL: https://issues.apache.org/jira/browse/OMID-192
> Project: Phoenix Omid
> Issue Type: Bug
>Reporter: Richard Antal
>Assignee: Istvan Toth
>Priority: Major
>
> When I started the the **_omid.sh create-hbase-commit-table
> _I got the following exception:
> {{}}
> {code:java}
> Error: A JNI error has occurred, please check your installation and try again
> Exception in thread "main" java.lang.NoClassDefFoundError:
> com/beust/jcommander/ParameterException{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6245) Update tephra dependency version to 0.16.0
[ https://issues.apache.org/jira/browse/PHOENIX-6245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-6245. -- Fix Version/s: 4.16.0 5.1.0 Resolution: Fixed Committed to master and 4.x Thanks for the reviews Viraj and shahrs87. > Update tephra dependency version to 0.16.0 > -- > > Key: PHOENIX-6245 > URL: https://issues.apache.org/jira/browse/PHOENIX-6245 > Project: Phoenix > Issue Type: Improvement > Components: core >Affects Versions: 5.1.0, 4.16.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 5.1.0, 4.16.0 > > > For master this mostly a cleanup, as the SNAPSHOT that we were using had > already basically the same code. > For 4.x this is a meaningful update, with real fixes and enabling Tephra > support for HBase 1.5 and 1.6. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OMID-192) fix missing jcommander dependency
[
https://issues.apache.org/jira/browse/OMID-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated OMID-192:
-
Fix Version/s: 1.0.3
Affects Version/s: 1.0.2
> fix missing jcommander dependency
> -
>
> Key: OMID-192
> URL: https://issues.apache.org/jira/browse/OMID-192
> Project: Phoenix Omid
> Issue Type: Bug
>Affects Versions: 1.0.2
>Reporter: Richard Antal
>Assignee: Istvan Toth
>Priority: Major
> Fix For: 1.0.3
>
>
> When I started the the _omid.sh create-hbase-commit-table
> I got the following exception:
> {code:java}
> Error: A JNI error has occurred, please check your installation and try again
> Exception in thread "main" java.lang.NoClassDefFoundError:
> com/beust/jcommander/ParameterException{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OMID-192) fix missing jcommander dependency
[
https://issues.apache.org/jira/browse/OMID-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated OMID-192:
-
Priority: Blocker (was: Major)
> fix missing jcommander dependency
> -
>
> Key: OMID-192
> URL: https://issues.apache.org/jira/browse/OMID-192
> Project: Phoenix Omid
> Issue Type: Bug
>Affects Versions: 1.0.2
>Reporter: Richard Antal
>Assignee: Istvan Toth
>Priority: Blocker
> Fix For: 1.0.3
>
>
> When I started the the _omid.sh create-hbase-commit-table
> I got the following exception:
> {code:java}
> Error: A JNI error has occurred, please check your installation and try again
> Exception in thread "main" java.lang.NoClassDefFoundError:
> com/beust/jcommander/ParameterException{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (OMID-192) fix missing jcommander dependency
[
https://issues.apache.org/jira/browse/OMID-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth resolved OMID-192.
--
Resolution: Fixed
> fix missing jcommander dependency
> -
>
> Key: OMID-192
> URL: https://issues.apache.org/jira/browse/OMID-192
> Project: Phoenix Omid
> Issue Type: Bug
>Affects Versions: 1.0.2
>Reporter: Richard Antal
>Assignee: Istvan Toth
>Priority: Major
> Fix For: 1.0.3
>
>
> When I started the the _omid.sh create-hbase-commit-table
> I got the following exception:
> {code:java}
> Error: A JNI error has occurred, please check your installation and try again
> Exception in thread "main" java.lang.NoClassDefFoundError:
> com/beust/jcommander/ParameterException{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OMID-191) Fix missing executable permission because of MASSEMBLY-941
[ https://issues.apache.org/jira/browse/OMID-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated OMID-191: - Affects Version/s: 1.0.2 > Fix missing executable permission because of MASSEMBLY-941 > -- > > Key: OMID-191 > URL: https://issues.apache.org/jira/browse/OMID-191 > Project: Phoenix Omid > Issue Type: Bug >Affects Versions: 1.0.2 >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Blocker > Fix For: 1.0.3 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OMID-192) fix missing jcommander dependency
[
https://issues.apache.org/jira/browse/OMID-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17244991#comment-17244991
]
Istvan Toth commented on OMID-192:
--
Committed to master.
Thanks for finding the bug and the review [~RichardAntal]
> fix missing jcommander dependency
> -
>
> Key: OMID-192
> URL: https://issues.apache.org/jira/browse/OMID-192
> Project: Phoenix Omid
> Issue Type: Bug
>Affects Versions: 1.0.2
>Reporter: Richard Antal
>Assignee: Istvan Toth
>Priority: Blocker
> Fix For: 1.0.3
>
>
> When I started the the _omid.sh create-hbase-commit-table
> I got the following exception:
> {code:java}
> Error: A JNI error has occurred, please check your installation and try again
> Exception in thread "main" java.lang.NoClassDefFoundError:
> com/beust/jcommander/ParameterException{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5728) ExplainPlan with plan as attributes object, use it for BaseStatsCollectorIT
[ https://issues.apache.org/jira/browse/PHOENIX-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-5728: - Fix Version/s: (was: 4.17.0) (was: 4.16.1) 4.16.0 Affects Version/s: (was: 4.15.1) 4.15.0 > ExplainPlan with plan as attributes object, use it for BaseStatsCollectorIT > --- > > Key: PHOENIX-5728 > URL: https://issues.apache.org/jira/browse/PHOENIX-5728 > Project: Phoenix > Issue Type: Sub-task >Affects Versions: 4.15.0, 5.1.0 >Reporter: Viraj Jasani >Assignee: Viraj Jasani >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5728.4.x.000.patch, > PHOENIX-5728.master.000.patch, PHOENIX-5728.master.000.patch, > PHOENIX-5728.master.001.patch > > > Provide -golden files- attributes based object for QueryPlan result > comparison for all abstract test class BaseStatsCollectorIT that includes > tests of all stats collections including: > * NamespaceDisabledStatsCollectorIT > * NamespaceEnabledStatsCollectorIT > * NonTxStatsCollectorIT > * TxStatsCollectorIT > Object based ExplainPlan can be useful for quite precise comparison of > individual and relevant plan attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6137) Update Omid to 1.0.2 and Tephra to 0.16 in 4.x
[ https://issues.apache.org/jira/browse/PHOENIX-6137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-6137. -- Fix Version/s: 4.16.0 Resolution: Fixed Both done together with master. > Update Omid to 1.0.2 and Tephra to 0.16 in 4.x > -- > > Key: PHOENIX-6137 > URL: https://issues.apache.org/jira/browse/PHOENIX-6137 > Project: Phoenix > Issue Type: Task > Components: core >Affects Versions: 4.16.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 4.16.0 > > > On master, we are using SNAPSHOT versions of Omid and Tephra due to the > ongoing PHOENIX-6010 work. > As 4.x is not affected, it still uses the current released versions of Omid > and Tephra. > (Which means no HBase 1.5+ for Tephra, but it is a known issue) > This ticket is partly a reminder to do this, and a place to discuss it, as > well as an umbrella ticket where I plan to collect the JIRAs that also need > to be ported to 4.x for the update. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6248) Update hive-connector docs
Istvan Toth created PHOENIX-6248: Summary: Update hive-connector docs Key: PHOENIX-6248 URL: https://issues.apache.org/jira/browse/PHOENIX-6248 Project: Phoenix Issue Type: Task Components: connectors, hive-connector Affects Versions: connectors-6.0.0 Reporter: Istvan Toth Assignee: Istvan Toth We need to update several things in the hive connectors docs - Building from connectors repo - Optionally setting Hbase/Hadoop versions while building - How the included HBase connector in 3.1.2 is ancient and incompatbile with Phoenix - How to replace HBase in Hive (which kills HBase connector) - need to add the new hbase-zookeeper.jar as well - HIVE_AUX_JARS_PATH is a DIRCETORY, where only the connector can be present - internal tables are not supported with Hive 3 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-5787) Do not package hive dependencies into phoenix-hive jar
[ https://issues.apache.org/jira/browse/PHOENIX-5787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-5787. -- Fix Version/s: connectors-6.0.0 Resolution: Fixed Committed. Thanks for the review [~elserj] > Do not package hive dependencies into phoenix-hive jar > -- > > Key: PHOENIX-5787 > URL: https://issues.apache.org/jira/browse/PHOENIX-5787 > Project: Phoenix > Issue Type: Bug > Components: connectors, hive-connector >Affects Versions: connectors-6.0.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: connectors-6.0.0 > > > Phoenix and hive share a lot of dependencies, starting with hadoop and hbase. > We are shading all phoenix dependencies into the phoenix-hive connector, that > regularly case classpath/version mismatch problems with hive. > Instead of trying to resolve these one by one, exclude/shade all dependencies > from phoenix-jar that are available on the hive classpath. > The most critcal of these are the hadoop and hbase transitive dependencies. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6249) Create shaded phoenix-spark connector jar
Istvan Toth created PHOENIX-6249: Summary: Create shaded phoenix-spark connector jar Key: PHOENIX-6249 URL: https://issues.apache.org/jira/browse/PHOENIX-6249 Project: Phoenix Issue Type: Task Components: connectors, spark-connector Affects Versions: connectors-6.0.0 Reporter: Istvan Toth Assignee: Istvan Toth Create shaded phoenix-spark connector JAR. Since connectors have been split, we do not have the spark connector shaded into phoenix-client. Create shaded connector for spark that takes Hadoop from the spark classpath (thus minimizing the chances of classpath conflicts) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6249) Create shaded phoenix-spark connector jar
[ https://issues.apache.org/jira/browse/PHOENIX-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-6249: - Description: Since connectors have been split, we do not have the spark connector shaded into phoenix-client. Create shaded connector for spark that takes Hadoop from the spark classpath (thus minimizing the chances of classpath conflicts) was: Create shaded phoenix-spark connector JAR. Since connectors have been split, we do not have the spark connector shaded into phoenix-client. Create shaded connector for spark that takes Hadoop from the spark classpath (thus minimizing the chances of classpath conflicts) > Create shaded phoenix-spark connector jar > - > > Key: PHOENIX-6249 > URL: https://issues.apache.org/jira/browse/PHOENIX-6249 > Project: Phoenix > Issue Type: Task > Components: connectors, spark-connector >Affects Versions: connectors-6.0.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > > Since connectors have been split, we do not have the spark connector shaded > into phoenix-client. > Create shaded connector for spark that takes Hadoop from the spark classpath > (thus minimizing the chances of classpath conflicts) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-5202) Create uber client jar that has existing phoenix connectors
[ https://issues.apache.org/jira/browse/PHOENIX-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-5202. -- Assignee: Istvan Toth Resolution: Won't Do Feel free to reopen and start a discussion about it [~tdsilva] > Create uber client jar that has existing phoenix connectors > --- > > Key: PHOENIX-5202 > URL: https://issues.apache.org/jira/browse/PHOENIX-5202 > Project: Phoenix > Issue Type: New Feature >Reporter: Thomas D'Silva >Assignee: Istvan Toth >Priority: Major > > similar to how the phoenix-client jar included dependencies on phoenix-flume, > phoenix-spark etc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6253) Change shaded connector jar naming convention
Istvan Toth created PHOENIX-6253: Summary: Change shaded connector jar naming convention Key: PHOENIX-6253 URL: https://issues.apache.org/jira/browse/PHOENIX-6253 Project: Phoenix Issue Type: Improvement Components: connectors Affects Versions: connectors-6.0.0 Reporter: Istvan Toth Assignee: Istvan Toth Currently we distinguish the shaded and unshaded connector JARs by moving the version about. I.e phoenix5-hive-6.0.0 jar is the unshaded JAR, while phoenix5-6.0.0-hive.jar is the shaded one. This is unintuitive, and we have already dropped this convention in core. We could use something like: phoenix5-spark-6.0.0.jar: the unshaded connector JAR phoenix5-spark-connector-6.0.0.jar : the default shaded connector JAR phoenix5-spark-connector-byo-hbase-6.0.0.jar : alternative shaded connector JAR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6260) Omid exclusions are incomplete
Istvan Toth created PHOENIX-6260: Summary: Omid exclusions are incomplete Key: PHOENIX-6260 URL: https://issues.apache.org/jira/browse/PHOENIX-6260 Project: Phoenix Issue Type: Bug Components: core Affects Versions: 5.1.0 Reporter: Istvan Toth Assignee: Istvan Toth Phoenix 5 pulls org.apache.omid:omid-hbase-common-hbase1.x This seems to be caused by the incomplete Omid exclusion definitions. This really should be fixed in Omid in the long term, so that the exclusions are not needed, but short term we need to amend the exclusion list. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6249) Create shaded phoenix-spark connector jar
[ https://issues.apache.org/jira/browse/PHOENIX-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-6249. -- Fix Version/s: connectors-6.0.0 Resolution: Fixed Committed to master. Thanks for the review [~rajeshbabu] > Create shaded phoenix-spark connector jar > - > > Key: PHOENIX-6249 > URL: https://issues.apache.org/jira/browse/PHOENIX-6249 > Project: Phoenix > Issue Type: Task > Components: connectors, spark-connector >Affects Versions: connectors-6.0.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: connectors-6.0.0 > > > Since connectors have been split, we do not have the spark connector shaded > into phoenix-client. > Create shaded connector for spark that takes Hadoop from the spark classpath > (thus minimizing the chances of classpath conflicts) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6260) Omid exclusions are incomplete
[ https://issues.apache.org/jira/browse/PHOENIX-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-6260. -- Fix Version/s: 5.1.0 Resolution: Fixed Committed to master. Does not apply to 4.x. Thanks for the review [~vjasani] > Omid exclusions are incomplete > -- > > Key: PHOENIX-6260 > URL: https://issues.apache.org/jira/browse/PHOENIX-6260 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 5.1.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 5.1.0 > > > Phoenix 5 pulls org.apache.omid:omid-hbase-common-hbase1.x > This seems to be caused by the incomplete Omid exclusion definitions. > This really should be fixed in Omid in the long term, so that the exclusions > are not needed, but short term we need to amend the exclusion list. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6253) Change shaded connector jar naming convention
[ https://issues.apache.org/jira/browse/PHOENIX-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-6253: - Description: Currently we distinguish the shaded and unshaded connector JARs by moving the version about. I.e phoenix5-hive-6.0.0 jar is the unshaded JAR, while phoenix5-6.0.0-hive.jar is the shaded one. This is unintuitive, and we have already dropped this convention in core. We could use something like: -phoenix5-spark-6.0.0.jar: the unshaded connector JAR phoenix5-spark-connector-6.0.0.jar : the default shaded connector JAR phoenix5-spark-connector-byo-hbase-6.0.0.jar : alternative shaded connector JAR.- phoenix5-spark-6.0.0.jar: the unshaded connector JAR phoenix5-spark-6.0.0-shaded.jar : the default shaded connector JAR phoenix5-spark-6.0.0-shaded-byo-hbase.jar : alternative shaded connector JAR. was: Currently we distinguish the shaded and unshaded connector JARs by moving the version about. I.e phoenix5-hive-6.0.0 jar is the unshaded JAR, while phoenix5-6.0.0-hive.jar is the shaded one. This is unintuitive, and we have already dropped this convention in core. We could use something like: phoenix5-spark-6.0.0.jar: the unshaded connector JAR phoenix5-spark-connector-6.0.0.jar : the default shaded connector JAR phoenix5-spark-connector-byo-hbase-6.0.0.jar : alternative shaded connector JAR. > Change shaded connector jar naming convention > - > > Key: PHOENIX-6253 > URL: https://issues.apache.org/jira/browse/PHOENIX-6253 > Project: Phoenix > Issue Type: Improvement > Components: connectors >Affects Versions: connectors-6.0.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > > Currently we distinguish the shaded and unshaded connector JARs by moving the > version about. I.e phoenix5-hive-6.0.0 jar is the unshaded JAR, while > phoenix5-6.0.0-hive.jar is the shaded one. > This is unintuitive, and we have already dropped this convention in core. > We could use something like: > -phoenix5-spark-6.0.0.jar: the unshaded connector JAR > phoenix5-spark-connector-6.0.0.jar : the default shaded connector JAR > phoenix5-spark-connector-byo-hbase-6.0.0.jar : alternative shaded connector > JAR.- > phoenix5-spark-6.0.0.jar: the unshaded connector JAR > phoenix5-spark-6.0.0-shaded.jar : the default shaded connector JAR > phoenix5-spark-6.0.0-shaded-byo-hbase.jar : alternative shaded connector JAR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6253) Change shaded connector jar naming convention
[ https://issues.apache.org/jira/browse/PHOENIX-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-6253: - Description: Currently we distinguish the shaded and unshaded connector JARs by moving the version about. I.e phoenix5-hive-6.0.0 jar is the unshaded JAR, while phoenix5-6.0.0-hive.jar is the shaded one. This is unintuitive, and we have already dropped this convention in core. We could use something like: -phoenix5-spark-6.0.0.jar: the unshaded connector JAR- -phoenix5-spark-connector-6.0.0.jar : the default shaded connector JAR- -phoenix5-spark-connector-byo-hbase-6.0.0.jar : alternative shaded connector JAR.- phoenix5-spark-6.0.0.jar: the unshaded connector JAR phoenix5-spark-6.0.0-shaded.jar : the default shaded connector JAR phoenix5-spark-6.0.0-shaded-byo-hbase.jar : alternative shaded connector JAR. was: Currently we distinguish the shaded and unshaded connector JARs by moving the version about. I.e phoenix5-hive-6.0.0 jar is the unshaded JAR, while phoenix5-6.0.0-hive.jar is the shaded one. This is unintuitive, and we have already dropped this convention in core. We could use something like: -phoenix5-spark-6.0.0.jar: the unshaded connector JAR phoenix5-spark-connector-6.0.0.jar : the default shaded connector JAR phoenix5-spark-connector-byo-hbase-6.0.0.jar : alternative shaded connector JAR.- phoenix5-spark-6.0.0.jar: the unshaded connector JAR phoenix5-spark-6.0.0-shaded.jar : the default shaded connector JAR phoenix5-spark-6.0.0-shaded-byo-hbase.jar : alternative shaded connector JAR. > Change shaded connector jar naming convention > - > > Key: PHOENIX-6253 > URL: https://issues.apache.org/jira/browse/PHOENIX-6253 > Project: Phoenix > Issue Type: Improvement > Components: connectors >Affects Versions: connectors-6.0.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > > Currently we distinguish the shaded and unshaded connector JARs by moving the > version about. I.e phoenix5-hive-6.0.0 jar is the unshaded JAR, while > phoenix5-6.0.0-hive.jar is the shaded one. > This is unintuitive, and we have already dropped this convention in core. > We could use something like: > -phoenix5-spark-6.0.0.jar: the unshaded connector JAR- > -phoenix5-spark-connector-6.0.0.jar : the default shaded connector JAR- > -phoenix5-spark-connector-byo-hbase-6.0.0.jar : alternative shaded connector > JAR.- > phoenix5-spark-6.0.0.jar: the unshaded connector JAR > phoenix5-spark-6.0.0-shaded.jar : the default shaded connector JAR > phoenix5-spark-6.0.0-shaded-byo-hbase.jar : alternative shaded connector JAR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6261) Reorganise project structure to make mvn versions:set work
[ https://issues.apache.org/jira/browse/PHOENIX-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-6261. -- Fix Version/s: 4.16.0 connectors-6.0.0 5.1.0 Resolution: Fixed Committed to master and 4.x The connectors patch has already been committed. Thanks for the patches [~RichardAntal] and the reviews [~rajeshbabu]. > Reorganise project structure to make mvn versions:set work > -- > > Key: PHOENIX-6261 > URL: https://issues.apache.org/jira/browse/PHOENIX-6261 > Project: Phoenix > Issue Type: Task > Components: connectors, core >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > Fix For: 5.1.0, connectors-6.0.0, 4.16.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6272) PHOENIX-5592 introduces Dummy.java without ASF license
Istvan Toth created PHOENIX-6272: Summary: PHOENIX-5592 introduces Dummy.java without ASF license Key: PHOENIX-6272 URL: https://issues.apache.org/jira/browse/PHOENIX-6272 Project: Phoenix Issue Type: Bug Components: core Affects Versions: master Reporter: Istvan Toth PHOENIX-5592 introduces a Dummy.java test file. It contains a commented out stub that could perhaps be used as a template, but more importantly it misses an ASF Header. If this is was committed unintentionally, it should be removed, if it thought to be useful as a template and kept, then at least the proper ASF license header should be added. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OMID-188) Fix "inconsistent module metadata found" when using hbase-2
[
https://issues.apache.org/jira/browse/OMID-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth reassigned OMID-188:
Fix Version/s: 1.0.3
Release Note:
The maven artifact structure has changed.
Every artifact is built is built separately for HBase 1 and 2. You will need to
add the -hbase-1.x or -hbase-2.x suffix to every Omid artifact that you depend
on.
You no longer need to specify exclusions when using the HBase 2.x artifacts.
Affects Version/s: 1.0.2
Assignee: Chia-Ping Tsai
> Fix "inconsistent module metadata found" when using hbase-2
> ---
>
> Key: OMID-188
> URL: https://issues.apache.org/jira/browse/OMID-188
> Project: Phoenix Omid
> Issue Type: Bug
>Affects Versions: 1.0.2
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Major
> Fix For: 1.0.3
>
>
> the full message is shown below:
> {quote}
> What went wrong:
> Execution failed for task ':ohara-common:compileJava'.
> > Could not resolve all files for configuration
> > ':ohara-common:compileClasspath'.
> > Could not resolve org.apache.omid:omid-hbase-client-hbase2.x:1.0.1.
> Required by:
> project :ohara-common
> > Could not resolve org.apache.omid:omid-hbase-client-hbase2.x:1.0.1.
> > inconsistent module metadata found. Descriptor:
> org.apache.omid:omid-hbase-client-hbase1.x:1.0.1 Errors: bad module name:
> expected='omid-hbase-client-hbase2.x' found='omid-hbase-client-hbase1.x'
> {quote}
> The root cause is the parent pom still uses profile "hbase-1" so the sub pom
> has postfix " hbase-1".
> In order to resolve this issue, it seems to me the artifactId of parent
> should have postfix and the pom of parent should be rewrite according to
> profile (when building release). That makes sub pom can find correct parent
> pom.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (OMID-188) Fix "inconsistent module metadata found" when using hbase-2
[
https://issues.apache.org/jira/browse/OMID-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth resolved OMID-188.
--
Resolution: Fixed
Committed.
See the release notes filed for the artifact changes.
Thank you [~chia7712].
> Fix "inconsistent module metadata found" when using hbase-2
> ---
>
> Key: OMID-188
> URL: https://issues.apache.org/jira/browse/OMID-188
> Project: Phoenix Omid
> Issue Type: Bug
>Affects Versions: 1.0.2
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Major
> Fix For: 1.0.3
>
>
> the full message is shown below:
> {quote}
> What went wrong:
> Execution failed for task ':ohara-common:compileJava'.
> > Could not resolve all files for configuration
> > ':ohara-common:compileClasspath'.
> > Could not resolve org.apache.omid:omid-hbase-client-hbase2.x:1.0.1.
> Required by:
> project :ohara-common
> > Could not resolve org.apache.omid:omid-hbase-client-hbase2.x:1.0.1.
> > inconsistent module metadata found. Descriptor:
> org.apache.omid:omid-hbase-client-hbase1.x:1.0.1 Errors: bad module name:
> expected='omid-hbase-client-hbase2.x' found='omid-hbase-client-hbase1.x'
> {quote}
> The root cause is the parent pom still uses profile "hbase-1" so the sub pom
> has postfix " hbase-1".
> In order to resolve this issue, it seems to me the artifactId of parent
> should have postfix and the pom of parent should be rewrite according to
> profile (when building release). That makes sub pom can find correct parent
> pom.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (PHOENIX-6279) Clarify supported HBase 1.3 and 1.4 patch releases
Istvan Toth created PHOENIX-6279: Summary: Clarify supported HBase 1.3 and 1.4 patch releases Key: PHOENIX-6279 URL: https://issues.apache.org/jira/browse/PHOENIX-6279 Project: Phoenix Issue Type: Bug Components: core Affects Versions: 4.x Reporter: Istvan Toth Playing around the with the hbase.version property, I noticed that even though we claim to support HBase 1.3.0 and 1.4.0, the current 4.x branch doesn't actually compile with either version. Find the first patch levels that we actually support for these HBase minor branches, and update the documentation / pom description. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6280) Support HBase 2.4
Istvan Toth created PHOENIX-6280: Summary: Support HBase 2.4 Key: PHOENIX-6280 URL: https://issues.apache.org/jira/browse/PHOENIX-6280 Project: Phoenix Issue Type: New Feature Components: core Affects Versions: 5.1.0 Reporter: Istvan Toth Assignee: Istvan Toth -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6281) Remove hbase-compat-1.x from Phoenix 5.x
[ https://issues.apache.org/jira/browse/PHOENIX-6281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-6281. -- Fix Version/s: 5.1.0 Resolution: Fixed Committed to master. Thank you [~vjasani]. > Remove hbase-compat-1.x from Phoenix 5.x > > > Key: PHOENIX-6281 > URL: https://issues.apache.org/jira/browse/PHOENIX-6281 > Project: Phoenix > Issue Type: Task >Reporter: Viraj Jasani >Assignee: Viraj Jasani >Priority: Major > Fix For: 5.1.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6282) Generate PB files inline with build and remove checked in files
[ https://issues.apache.org/jira/browse/PHOENIX-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-6282. -- Resolution: Fixed Committed to master and 4.x Thank you [~vjasani] > Generate PB files inline with build and remove checked in files > --- > > Key: PHOENIX-6282 > URL: https://issues.apache.org/jira/browse/PHOENIX-6282 > Project: Phoenix > Issue Type: Task >Reporter: Viraj Jasani >Assignee: Viraj Jasani >Priority: Major > Fix For: 5.1.0, 4.16.0 > > > We can use a new PB maven plugin to generate PB files with build rather than > checking in generated PB files (~2 MB as of now) in source code. The plugin > also provides an optimization for protoc invocation. With checkStaleness > property, protoc will not be invoked if no .proto file is changed. Only > separate build will invoke protoc and generate PB files inline. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6283) MutableIndexExtendedIT#testCompactDisabledIndex consistently fails with HBase 2.3
Istvan Toth created PHOENIX-6283: Summary: MutableIndexExtendedIT#testCompactDisabledIndex consistently fails with HBase 2.3 Key: PHOENIX-6283 URL: https://issues.apache.org/jira/browse/PHOENIX-6283 Project: Phoenix Issue Type: Bug Components: core Affects Versions: 5.1.0 Reporter: Istvan Toth This seems to be related to the Indexing rebase. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6283) MutableIndexExtendedIT#testCompactDisabledIndex consistently fails with HBase 2.3
[ https://issues.apache.org/jira/browse/PHOENIX-6283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth reassigned PHOENIX-6283: Assignee: Istvan Toth > MutableIndexExtendedIT#testCompactDisabledIndex consistently fails with HBase > 2.3 > - > > Key: PHOENIX-6283 > URL: https://issues.apache.org/jira/browse/PHOENIX-6283 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 5.1.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Blocker > > This seems to be related to the Indexing rebase. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6104) SplitSystemCatalogIT tests very unstable with Hbase 2.3
[ https://issues.apache.org/jira/browse/PHOENIX-6104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth reassigned PHOENIX-6104: Assignee: Istvan Toth > SplitSystemCatalogIT tests very unstable with Hbase 2.3 > --- > > Key: PHOENIX-6104 > URL: https://issues.apache.org/jira/browse/PHOENIX-6104 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 5.1.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Attachments: 6104-testouput.log > > > The failure is in the test preparation code, where we split the system > catalog table, and it seems to be a HBase issue, rather than a Phoenix one, > but we need to track the issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6104) SplitSystemCatalogIT tests very unstable with Hbase 2.3
[ https://issues.apache.org/jira/browse/PHOENIX-6104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-6104. -- Fix Version/s: 5.1.0 Resolution: Fixed Committed to master. Thanks for doing most of the work, and the review [~vjasani] > SplitSystemCatalogIT tests very unstable with Hbase 2.3 > --- > > Key: PHOENIX-6104 > URL: https://issues.apache.org/jira/browse/PHOENIX-6104 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 5.1.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 5.1.0 > > Attachments: 6104-testouput.log > > > The failure is in the test preparation code, where we split the system > catalog table, and it seems to be a HBase issue, rather than a Phoenix one, > but we need to track the issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6286) Extend syscat RegionSplitPolicies from the default Policy for the HBase branch
Istvan Toth created PHOENIX-6286: Summary: Extend syscat RegionSplitPolicies from the default Policy for the HBase branch Key: PHOENIX-6286 URL: https://issues.apache.org/jira/browse/PHOENIX-6286 Project: Phoenix Issue Type: Bug Reporter: Istvan Toth Assignee: Istvan Toth The Syscat-specific Policies are exended from ConstantSizeRegionSplitPolicy, instead of the default Policy for HBase. AFAICT this has historical, rather than technical reasons. Base our policies on the default policy for the supported HBase branch. -- This message was sent by Atlassian Jira (v8.3.4#803005)
