[jira] [Updated] (PHOENIX-6118) Multi Tenant Workloads using PHERF

[ https://issues.apache.org/jira/browse/PHOENIX-6118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Isaac updated PHOENIX-6118: - Parent: PHOENIX-6406 Issue Type: Sub-task (was: Improvement) > Multi Tenant Workloads

[jira] [Created] (PHOENIX-6406) PHERF Improvements

Jacob Isaac created PHOENIX-6406: Summary: PHERF Improvements Key: PHOENIX-6406 URL: https://issues.apache.org/jira/browse/PHOENIX-6406 Project: Phoenix Issue Type: Improvement Affects Ve

Re: [DISCUSS] HBase 2.2.5 public maven artifacts are incompatible with Hadoop 3

> To further complicate matters, we may have similar incompatibilities > between Hadoop 3.0 and 3.1, as I have seen similar errors when building > Phoenix with Hadoop 3.1 This is unfortunate. Anyone know of Hadoop releasing plans for 3.0.x? Perhaps you can ignore it and go straight to 3.1.x. And p

[GitHub] [phoenix-omid] chrajeshbabu closed pull request #89: OMID-198 Replace static ports used for TSO server with random ports i…

chrajeshbabu closed pull request #89: URL: https://github.com/apache/phoenix-omid/pull/89 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to

[jira] [Resolved] (OMID-167) fix flaky TestTSOChannelHandlerNetty

[ https://issues.apache.org/jira/browse/OMID-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved OMID-167. -- Fix Version/s: 1.0.3 Resolution: Duplicate OMID-198 has a complete fix for this issue with dynamic

[GitHub] [phoenix-omid] stoty commented on pull request #74: OMID-167 fix flaky TestTSOChannelHandlerNetty

stoty commented on pull request #74: URL: https://github.com/apache/phoenix-omid/pull/74#issuecomment-792790258 Closing this as we have a fix for the root cause with dynamic port allocation. This is an automated message from

Re: https://issues.apache.org/jira/browse/HBASE-25644

Hi Anoop, Better to change in Phoenix irrespective of HBase dependency as you mentioned set small only when really meeting small scan requirement. Usually when ever new HBase release someone take a lead and try to change to latest version. But now just we need to add a profile with the newer vers

[jira] [Resolved] (OMID-198) Replace static ports used for TSO server with random ports in the tests

[ https://issues.apache.org/jira/browse/OMID-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla resolved OMID-198. -- Resolution: Fixed Pushed to master. Thanks for review [~stoty]. > Replace static

https://issues.apache.org/jira/browse/HBASE-25644

This bug is fixed now. But how often will we change the HBase client version in Phoenix pom? Will it be better to have a mitigation in Phoenix code also. Simple change in ScanUtil.java to have a isSmall() true check before calling newScan.setSmall(scan.isSmall()); This will create a big perf is

[jira] [Assigned] (PHOENIX-6398) Returns uniform SQL dialect in calcite for the PQS

[ https://issues.apache.org/jira/browse/PHOENIX-6398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth reassigned PHOENIX-6398: Assignee: Cong Luo > Returns uniform SQL dialect in calcite for the PQS > --

Re: Getting exception when trying to use/integrate phoenix-client-hbase-1.6-4.16.0.jar in a multi-module project

Hi Jacob ! Yes, It looks like PHOENIX-6144 You can try using phoenix-core instead. For 5.x, I plan to explore building a phoenix-client variant that can use external shaded hadoop-client and hbase-client JARs, I'm not sure if have the same protobuf client version problem in 4.x. Istvan On Thu,