[jira] [Updated] (PHOENIX-5896) Implement incremental rebuild along the failed regions in IndexTool
[ https://issues.apache.org/jira/browse/PHOENIX-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam updated PHOENIX-5896: Attachment: (was: PHOENIX-5896.4.x.add1.patch) > Implement incremental rebuild along the failed regions in IndexTool > --- > > Key: PHOENIX-5896 > URL: https://issues.apache.org/jira/browse/PHOENIX-5896 > Project: Phoenix > Issue Type: Improvement >Reporter: Swaroopa Kadam >Assignee: Swaroopa Kadam >Priority: Major > Attachments: PHOENIX-5896.4.x.add0.patch, PHOENIX-5896.4.x.v1.patch, > PHOENIX-5896.4.x.v2.patch, PHOENIX-5896.4.x.v3.patch, > PHOENIX-5896.4.x.v4.patch > > Time Spent: 2.5h > Remaining Estimate: 0h > > As we run the index tool on indexes to be rebuilt after the upgrade, it > spends some time in rescanning successful regions from the last rebuild. We > want to make the index tool a little smarter to not rebuild rows from the > regions that were found in the PIT_result table from the last rebuild. > PIT_result logs region info if it was successfully rebuilt in the last run. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5896) Implement incremental rebuild along the failed regions in IndexTool
[ https://issues.apache.org/jira/browse/PHOENIX-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam updated PHOENIX-5896: Attachment: (was: PHOENIX-5896.4.x.add.patch) > Implement incremental rebuild along the failed regions in IndexTool > --- > > Key: PHOENIX-5896 > URL: https://issues.apache.org/jira/browse/PHOENIX-5896 > Project: Phoenix > Issue Type: Improvement >Reporter: Swaroopa Kadam >Assignee: Swaroopa Kadam >Priority: Major > Attachments: PHOENIX-5896.4.x.add1.patch, PHOENIX-5896.4.x.v1.patch, > PHOENIX-5896.4.x.v2.patch, PHOENIX-5896.4.x.v3.patch, > PHOENIX-5896.4.x.v4.patch > > Time Spent: 2.5h > Remaining Estimate: 0h > > As we run the index tool on indexes to be rebuilt after the upgrade, it > spends some time in rescanning successful regions from the last rebuild. We > want to make the index tool a little smarter to not rebuild rows from the > regions that were found in the PIT_result table from the last rebuild. > PIT_result logs region info if it was successfully rebuilt in the last run. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5896) Implement incremental rebuild along the failed regions in IndexTool
[ https://issues.apache.org/jira/browse/PHOENIX-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam updated PHOENIX-5896: Attachment: (was: PHOENIX-5896.4.x.add.patch) > Implement incremental rebuild along the failed regions in IndexTool > --- > > Key: PHOENIX-5896 > URL: https://issues.apache.org/jira/browse/PHOENIX-5896 > Project: Phoenix > Issue Type: Improvement >Reporter: Swaroopa Kadam >Assignee: Swaroopa Kadam >Priority: Major > Attachments: PHOENIX-5896.4.x.v1.patch, PHOENIX-5896.4.x.v2.patch, > PHOENIX-5896.4.x.v3.patch, PHOENIX-5896.4.x.v4.patch > > Time Spent: 2.5h > Remaining Estimate: 0h > > As we run the index tool on indexes to be rebuilt after the upgrade, it > spends some time in rescanning successful regions from the last rebuild. We > want to make the index tool a little smarter to not rebuild rows from the > regions that were found in the PIT_result table from the last rebuild. > PIT_result logs region info if it was successfully rebuilt in the last run. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5899) Index writes and verifications should contain information of underlying cause of failure
[ https://issues.apache.org/jira/browse/PHOENIX-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5899: Fix Version/s: 5.1.0 > Index writes and verifications should contain information of underlying cause > of failure > > > Key: PHOENIX-5899 > URL: https://issues.apache.org/jira/browse/PHOENIX-5899 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5899.4.x.001.patch, PHOENIX-5899.4.x.001.patch, > PHOENIX-5899.4.x.patch, PHOENIX-5899.4.x.patch, PHOENIX-5899.4.x.patch, > PHOENIX-5899.master.patch > > Time Spent: 40m > Remaining Estimate: 0h > > In case of any failures during index writes, rebuild and verify we simply > return > MultiIndexWriteFailureException without the underlying cause. This makes > finding the underlying root cause exceptionally hard. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-5907) Remove unused part from phoenix_utils.py
[ https://issues.apache.org/jira/browse/PHOENIX-5907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang reassigned PHOENIX-5907: --- Assignee: Guanghao Zhang > Remove unused part from phoenix_utils.py > > > Key: PHOENIX-5907 > URL: https://issues.apache.org/jira/browse/PHOENIX-5907 > Project: Phoenix > Issue Type: Improvement > Components: queryserver >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > > Seems the queryserver.py and phoenix_utils.py was copied from the original > phoenix project? There are something which is not needed for > phoenix-queryserver. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5907) Remove unused part from phoenix_utils.py
Guanghao Zhang created PHOENIX-5907: --- Summary: Remove unused part from phoenix_utils.py Key: PHOENIX-5907 URL: https://issues.apache.org/jira/browse/PHOENIX-5907 Project: Phoenix Issue Type: Improvement Components: queryserver Reporter: Guanghao Zhang Seems the queryserver.py and phoenix_utils.py was copied from the original phoenix project? There are something which is not needed for phoenix-queryserver. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5899) Index writes and verifications should contain information of underlying cause of failure
[ https://issues.apache.org/jira/browse/PHOENIX-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5899: Attachment: PHOENIX-5899.4.x.001.patch > Index writes and verifications should contain information of underlying cause > of failure > > > Key: PHOENIX-5899 > URL: https://issues.apache.org/jira/browse/PHOENIX-5899 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5899.4.x.001.patch, PHOENIX-5899.4.x.001.patch, > PHOENIX-5899.4.x.patch, PHOENIX-5899.4.x.patch, PHOENIX-5899.4.x.patch, > PHOENIX-5899.master.patch > > Time Spent: 20m > Remaining Estimate: 0h > > In case of any failures during index writes, rebuild and verify we simply > return > MultiIndexWriteFailureException without the underlying cause. This makes > finding the underlying root cause exceptionally hard. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5863) Upsert into view against a table with index throws exception when 4.14.3 client connects to 4.16 server
[ https://issues.apache.org/jira/browse/PHOENIX-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5863: Fix Version/s: 4.16.0 > Upsert into view against a table with index throws exception when 4.14.3 > client connects to 4.16 server > --- > > Key: PHOENIX-5863 > URL: https://issues.apache.org/jira/browse/PHOENIX-5863 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Sandeep Guggilam >Assignee: Sandeep Guggilam >Priority: Blocker > Fix For: 4.16.0 > > Attachments: PHOENIX-5863.4.x.v1.patch > > > Steps to reproduce: > # Bring up a 4.16 server ( current 4.x branch) > # Connect a 4.14.3 client to the server and execute below queries > # CREATE TABLE IF NOT EXISTS T1 (ID INTEGER NOT NULL PRIMARY KEY, V1 > VARCHAR(10)); > # CREATE INDEX T1_IDX ON T1(V1); > # CREATE VIEW T1_V1 (V2 INTEGER) AS SELECT * FROM T1 WHERE ID=1; > # UPSERT INTO T1_V1(ID, V1, V2) VALUES (1, 'abc', 1); //*This throws below > exception*** > *Error: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: > Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException: At least one > index write failed after retries,serverTimestamp=1587513404084,* > *at > org.apache.phoenix.util.ServerUtil.wrapInDoNotRetryIOException(ServerUtil.java:267)* > *at > org.apache.phoenix.hbase.index.write.TrackingParallelWriterIndexCommitter.write(TrackingParallelWriterIndexCommitter.java:249)* > *at > org.apache.phoenix.hbase.index.write.IndexWriter.write(IndexWriter.java:203)* > *at > org.apache.phoenix.hbase.index.IndexRegionObserver.doIndexWritesWithExceptions(IndexRegionObserver.java:1025)* > *at > org.apache.phoenix.hbase.index.IndexRegionObserver.doPre(IndexRegionObserver.java:1053)* > *at > org.apache.phoenix.hbase.index.IndexRegionObserver.preBatchMutateWithExceptions(IndexRegionObserver.java:938)* > *at > org.apache.phoenix.hbase.index.IndexRegionObserver.preBatchMutate(IndexRegionObserver.java:351)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$35.call(RegionCoprocessorHost.java:1024)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$RegionOperation.call(RegionCoprocessorHost.java:1742)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.execOperation(RegionCoprocessorHost.java:1827)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.execOperation(RegionCoprocessorHost.java:1783)* > *at > org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.preBatchMutate(RegionCoprocessorHost.java:1020)* > *at > org.apache.hadoop.hbase.regionserver.HRegion.doMiniBatchMutation(HRegion.java:3420)* > *at > org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:3158)* > *at > org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:3100)* > *at > org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:944)* > *at > org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:872)* > *at > org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2472)* > *at > org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:36812)* > *at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2399)* > *at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:124)* > *at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:311)* > *at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:291)* > *Caused by: > org.apache.phoenix.hbase.index.exception.MultiIndexWriteFailureException: > disableIndexOnFailure=false, Failed to write to multiple index tables: > [V2#I2|#I2]* > *at > org.apache.phoenix.hbase.index.write.TrackingParallelWriterIndexCommitter.write(TrackingParallelWriterIndexCommitter.java:245)* > *... 21 more* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5906) Use a recent version of maven-shade-plugin
[ https://issues.apache.org/jira/browse/PHOENIX-5906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Kyle Purtell updated PHOENIX-5906: - Summary: Use a recent version of maven-shade-plugin (was: Ask for a recent version of maven-shade-plugin) > Use a recent version of maven-shade-plugin > -- > > Key: PHOENIX-5906 > URL: https://issues.apache.org/jira/browse/PHOENIX-5906 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Andrew Kyle Purtell >Assignee: Andrew Kyle Purtell >Priority: Minor > Fix For: 4.16.0 > > > The configuration of maven-shade-plugin doesn't require a particular version. > Depending on Maven version, the downloaded plugin may be too old to handle > Java 8 bytecodes, which may come in from Hadoop 3 among other places. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5906) Ask for a recent version of maven-shade-plugin
Andrew Kyle Purtell created PHOENIX-5906: Summary: Ask for a recent version of maven-shade-plugin Key: PHOENIX-5906 URL: https://issues.apache.org/jira/browse/PHOENIX-5906 Project: Phoenix Issue Type: Bug Affects Versions: 4.16.0 Reporter: Andrew Kyle Purtell Assignee: Andrew Kyle Purtell Fix For: 4.16.0 The configuration of maven-shade-plugin doesn't require a particular version. Depending on Maven version, the downloaded plugin may be too old to handle Java 8 bytecodes, which may come in from Hadoop 3 among other places. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5899) Index writes and verifications should contain information of underlying cause of failure
[ https://issues.apache.org/jira/browse/PHOENIX-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5899: Attachment: PHOENIX-5899.master.patch > Index writes and verifications should contain information of underlying cause > of failure > > > Key: PHOENIX-5899 > URL: https://issues.apache.org/jira/browse/PHOENIX-5899 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5899.4.x.001.patch, PHOENIX-5899.4.x.patch, > PHOENIX-5899.4.x.patch, PHOENIX-5899.4.x.patch, PHOENIX-5899.master.patch > > Time Spent: 10m > Remaining Estimate: 0h > > In case of any failures during index writes, rebuild and verify we simply > return > MultiIndexWriteFailureException without the underlying cause. This makes > finding the underlying root cause exceptionally hard. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5905) Reset user to hbase by changing rpc context before getting user permissions on access controller service
[ https://issues.apache.org/jira/browse/PHOENIX-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-5905: - Attachment: PHOENIX-5905.patch > Reset user to hbase by changing rpc context before getting user permissions > on access controller service > - > > Key: PHOENIX-5905 > URL: https://issues.apache.org/jira/browse/PHOENIX-5905 > Project: Phoenix > Issue Type: Bug >Reporter: Rajeshbabu Chintaguntla >Assignee: Rajeshbabu Chintaguntla >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5905.patch > > > Currently we are calling getUserPermissions with hbase user directly on > access controller service which is not a rpc call. If we don't reset user > system user will be considered and might expect extra privileges to return > the user permissions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5905) Reset user to hbase by changing rpc context before getting user permissions on access controller service
Rajeshbabu Chintaguntla created PHOENIX-5905: Summary: Reset user to hbase by changing rpc context before getting user permissions on access controller service Key: PHOENIX-5905 URL: https://issues.apache.org/jira/browse/PHOENIX-5905 Project: Phoenix Issue Type: Bug Reporter: Rajeshbabu Chintaguntla Assignee: Rajeshbabu Chintaguntla Fix For: 5.1.0, 4.16.0 Currently we are calling getUserPermissions with hbase user directly on access controller service which is not a rpc call. If we don't reset user system user will be considered and might expect extra privileges to return the user permissions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5831) Make Phoenix queryserver scripts work with Python 3
[ https://issues.apache.org/jira/browse/PHOENIX-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5831: --- Attachment: PHOENIX-5831.master.v6.patch > Make Phoenix queryserver scripts work with Python 3 > --- > > Key: PHOENIX-5831 > URL: https://issues.apache.org/jira/browse/PHOENIX-5831 > Project: Phoenix > Issue Type: Bug > Components: queryserver >Affects Versions: queryserver-1.0.0 >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Critical > Fix For: queryserver-1.0.0 > > Attachments: PHOENIX-5831.master.v1.patch, > PHOENIX-5831.master.v2.patch, PHOENIX-5831.master.v3.patch, > PHOENIX-5831.master.v4.patch, PHOENIX-5831.master.v5.patch, > PHOENIX-5831.master.v6.patch > > > Python 2 is being retired in some environments now. We should make sure that > the Phoenix queryserver scripts work with Python 2 and 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5656) Make Phoenix scripts work with Python 3
[ https://issues.apache.org/jira/browse/PHOENIX-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5656: --- Attachment: PHOENIX-5656.master.v5.patch > Make Phoenix scripts work with Python 3 > --- > > Key: PHOENIX-5656 > URL: https://issues.apache.org/jira/browse/PHOENIX-5656 > Project: Phoenix > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: Richard Antal >Priority: Critical > Fix For: 5.1.0, 4.16.0 > > Attachments: 5656-4.x-HBase-1.5-untested.txt, > 5656-4.x-HBase-1.5-v3.txt, 5656-4.x-HBase-1.5-v4.txt, > PHOENIX-5656.4.x.v1.patch, PHOENIX-5656.4.x.v2.patch, > PHOENIX-5656.4.x.v3.patch, PHOENIX-5656.4.x.v4.patch, > PHOENIX-5656.4.x.v5.patch, PHOENIX-5656.master.v1.patch, > PHOENIX-5656.master.v2.patch, PHOENIX-5656.master.v3.patch, > PHOENIX-5656.master.v4.patch, PHOENIX-5656.master.v5.patch > > > Python 2 is being retired in some environments now. We should make sure that > the Phoenix scripts work with Python 2 and 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5656) Make Phoenix scripts work with Python 3
[ https://issues.apache.org/jira/browse/PHOENIX-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5656: --- Attachment: PHOENIX-5656.4.x.v5.patch > Make Phoenix scripts work with Python 3 > --- > > Key: PHOENIX-5656 > URL: https://issues.apache.org/jira/browse/PHOENIX-5656 > Project: Phoenix > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: Richard Antal >Priority: Critical > Fix For: 5.1.0, 4.16.0 > > Attachments: 5656-4.x-HBase-1.5-untested.txt, > 5656-4.x-HBase-1.5-v3.txt, 5656-4.x-HBase-1.5-v4.txt, > PHOENIX-5656.4.x.v1.patch, PHOENIX-5656.4.x.v2.patch, > PHOENIX-5656.4.x.v3.patch, PHOENIX-5656.4.x.v4.patch, > PHOENIX-5656.4.x.v5.patch, PHOENIX-5656.master.v1.patch, > PHOENIX-5656.master.v2.patch, PHOENIX-5656.master.v3.patch, > PHOENIX-5656.master.v4.patch, PHOENIX-5656.master.v5.patch > > > Python 2 is being retired in some environments now. We should make sure that > the Phoenix scripts work with Python 2 and 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5904) Add log if the configed kerberos principal login failed
Guanghao Zhang created PHOENIX-5904:
---
Summary: Add log if the configed kerberos principal login failed
Key: PHOENIX-5904
URL: https://issues.apache.org/jira/browse/PHOENIX-5904
Project: Phoenix
Issue Type: Improvement
Components: queryserver
Reporter: Guanghao Zhang
{code:java}
SecurityUtil.login(getConf(),
QueryServerProperties.QUERY_SERVER_KEYTAB_FILENAME_ATTRIB,
QueryServerProperties.QUERY_SERVER_KERBEROS_PRINCIPAL_ATTRIB, hostname);
LOG.info("Login successful.");
{code}
But SecurityUtil.login may return directly if
UserGroupInformation.isSecurityEnabled return false.
{code:java}
public static void login(final Configuration conf,
final String keytabFileKey, final String userNameKey, String hostname)
throws IOException {
if(!UserGroupInformation.isSecurityEnabled())
return;
String keytabFilename = conf.get(keytabFileKey);
if (keytabFilename == null || keytabFilename.length() == 0) {
throw new IOException("Running in secure mode, but config doesn't have a
keytab");
}
String principalConfig = conf.get(userNameKey, System
.getProperty("user.name"));
String principalName = SecurityUtil.getServerPrincipal(principalConfig,
hostname);
UserGroupInformation.loginUserFromKeytab(principalName, keytabFilename);
}
{code}
UserGroupInformation.isSecurityEnabled is configed by
*hadoop.security.authentication*. But the document only said need to config
*hbase.security.authentication*. So, I thought we need to add document about
this, too.
QueryServer doc: [https://phoenix.apache.org/server.html]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (PHOENIX-5826) Remove guava from queryserver
[ https://issues.apache.org/jira/browse/PHOENIX-5826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-5826. -- Fix Version/s: queryserver-1.0.0 Resolution: Fixed Committed. Thanks for the review, [~elserj] > Remove guava from queryserver > - > > Key: PHOENIX-5826 > URL: https://issues.apache.org/jira/browse/PHOENIX-5826 > Project: Phoenix > Issue Type: Improvement > Components: queryserver >Affects Versions: queryserver-1.0.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: queryserver-1.0.0 > > > The queryserver repo has to work with multiple phoenix branches. > HBase and Hadoop master has already migrated to guava27/28. > Queryserver has to work both with the 4.x branch, which will probably have to > stay on the old guava version, and master, which will have to be upgraded to > 28. > The queryserver codebase does not work with Guava 28. > The simplest way to solve this problem is to remove guava from the > queryserver modules. > Most of the guava uses are trivial to replace -, but unfortunately changing > the host information that load-balancer stores in zookeeper is a non backward > compatible change- . The HostAndPort object would have to be replaced by > something like InetSocketAddress . > Since we are before the first release of the unbundled queryserver, I think > that this a great time to get this done with minimal disruption to the users. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5903) Mark more hbase dependency's scope as provided for phoenix-server
[ https://issues.apache.org/jira/browse/PHOENIX-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated PHOENIX-5903: Attachment: PHOENIX-5903.master.001.patch > Mark more hbase dependency's scope as provided for phoenix-server > - > > Key: PHOENIX-5903 > URL: https://issues.apache.org/jira/browse/PHOENIX-5903 > Project: Phoenix > Issue Type: Improvement >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: PHOENIX-5903.master.001.patch > > > The new phoenix-server-*.jar seems bigger than before. It include many hbase > classes from hbase dependency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5903) Mark more hbase dependency's scope as provided for phoenix-server
[ https://issues.apache.org/jira/browse/PHOENIX-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated PHOENIX-5903: Affects Version/s: 5.1.0 > Mark more hbase dependency's scope as provided for phoenix-server > - > > Key: PHOENIX-5903 > URL: https://issues.apache.org/jira/browse/PHOENIX-5903 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.1.0 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Attachments: PHOENIX-5903.master.001.patch > > > The new phoenix-server-*.jar seems bigger than before. It include many hbase > classes from hbase dependency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5903) Mark more hbase dependency's scope as provided for phoenix-server
Guanghao Zhang created PHOENIX-5903: --- Summary: Mark more hbase dependency's scope as provided for phoenix-server Key: PHOENIX-5903 URL: https://issues.apache.org/jira/browse/PHOENIX-5903 Project: Phoenix Issue Type: Improvement Reporter: Guanghao Zhang The new phoenix-server-*.jar seems bigger than before. It include many hbase classes from hbase dependency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-5903) Mark more hbase dependency's scope as provided for phoenix-server
[ https://issues.apache.org/jira/browse/PHOENIX-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang reassigned PHOENIX-5903: --- Assignee: Guanghao Zhang > Mark more hbase dependency's scope as provided for phoenix-server > - > > Key: PHOENIX-5903 > URL: https://issues.apache.org/jira/browse/PHOENIX-5903 > Project: Phoenix > Issue Type: Improvement >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > > The new phoenix-server-*.jar seems bigger than before. It include many hbase > classes from hbase dependency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
