[jira] [Created] (PHOENIX-5456) IndexScrutinyTool slow for indexes on multitenant tables
Vincent Poon created PHOENIX-5456: - Summary: IndexScrutinyTool slow for indexes on multitenant tables Key: PHOENIX-5456 URL: https://issues.apache.org/jira/browse/PHOENIX-5456 Project: Phoenix Issue Type: Bug Affects Versions: 4.15.0, 5.1.0 Reporter: Vincent Poon The IndexScrutinyTool is doing full scans for index tables on multitenant tables. This is due to a change in PHOENIX-5089, where we added code to IndexColumnNames to skip a portion of the PK if the table is multitenant: https://github.com/apache/phoenix/commit/cc9754fff840f38d13c3adb0c963296959fff3fa#diff-0705645faa779229d00792c032ed377fR64 This causes scrutinies for global, non-view indexes on multitenant tables to skip the tenantId when generating the pk column list, thereby causing a full scan. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (PHOENIX-5455) IndexedKeyValue creation fails after HBASE-22034
[ https://issues.apache.org/jira/browse/PHOENIX-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey Jacoby reassigned PHOENIX-5455: Assignee: Geoffrey Jacoby > IndexedKeyValue creation fails after HBASE-22034 > > > Key: PHOENIX-5455 > URL: https://issues.apache.org/jira/browse/PHOENIX-5455 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.15.0, 4.14.3 >Reporter: Geoffrey Jacoby >Assignee: Geoffrey Jacoby >Priority: Blocker > Fix For: 4.15.0 > > > HBASE-22034 backported to branch-1 HBASE-21401 (adding several validation > checks to KeyValue creation) and HBASE-22032 (adding a null check for the row > key to KeyValue creation). It will first be released in HBase 1.5. > In Phoenix 4.14.2 we included PHOENIX-5188, which adds logic to initialize > IndexedKeyValues with the appropriate row key and offsets, so that it can > pass the new check in HBASE-22032. However, it did not correctly handle all > the checks in HBASE-21401. > When testing 4.14.3 of Phoenix with an HBase version containing HBASE-22034, > we see lots of errors like the following: > java.lang.IllegalArgumentException: Overflow when reading key length at > position=0, KeyValueBytesHex=foo, offset=0, length=3 > This will affect the future 4.15-HBase-1.5, and as well as any future release > of a 4.14.3 based on HBase-1.5 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (PHOENIX-5274) ConnectionQueryServiceImpl#ensureNamespaceCreated and ensureTableCreated should use HBase APIs that do not require ADMIN permissions for existence checks
[ https://issues.apache.org/jira/browse/PHOENIX-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Jain reassigned PHOENIX-5274: --- Assignee: Ankit Jain (was: Chinmay Kulkarni) > ConnectionQueryServiceImpl#ensureNamespaceCreated and ensureTableCreated > should use HBase APIs that do not require ADMIN permissions for existence > checks > - > > Key: PHOENIX-5274 > URL: https://issues.apache.org/jira/browse/PHOENIX-5274 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0, 4.14.2 >Reporter: Chinmay Kulkarni >Assignee: Ankit Jain >Priority: Major > Fix For: 5.0.0, 4.15.1 > > > [HBASE-22377|https://issues.apache.org/jira/browse/HBASE-22377] will > introduce a new API that does not require ADMIN permissions to check the > existence of a namespace. > Currently, CQSI#ensureNamespaceCreated calls > HBaseAdmin#getNamespaceDescriptor which eventually on the server causes a > call to AccessController#preGetNamespaceDescriptor. This tries to acquire > ADMIN permissions on the namespace. We should ideally use the new API > provided by HBASE-22377 which does not require the phoenix client to get > ADMIN permissions on the namespace. We should acquire ADMIN permissions only > in case we need to create the namespace if it doesn't already exist. > Similarly, CQSI#ensureTableCreated should first check the existence of a > table before trying to do HBaseAdmin#getTableDescriptor since this requires > CREATE and ADMIN permissions. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (PHOENIX-5416) Fix Array2IT testArrayRefToLiteral
[
https://issues.apache.org/jira/browse/PHOENIX-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swaroopa Kadam closed PHOENIX-5416.
---
bulk closing of jiras after 4.14.3 release
> Fix Array2IT testArrayRefToLiteral
> --
>
> Key: PHOENIX-5416
> URL: https://issues.apache.org/jira/browse/PHOENIX-5416
> Project: Phoenix
> Issue Type: Test
>Affects Versions: 4.15.0, 5.1.0, 4.14.3
>Reporter: Thomas D'Silva
>Assignee: Chinmay Kulkarni
>Priority: Major
> Fix For: 4.15.0, 5.1.0, 4.14.3
>
> Attachments: PHOENIX-5416-master-v2.patch,
> PHOENIX-5416-master-v3.patch, PHOENIX-5416-master-v4.patch,
> PHOENIX-5416-master.patch
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> {{Array2IT.testArrayRefToLiteral}} fails with an NPE
> {code}
> java.lang.NullPointerException
> at
> org.apache.phoenix.schema.types.PArrayDataTypeDecoder.positionAtArrayElement(PArrayDataTypeDecoder.java:124)
> at
> org.apache.phoenix.schema.types.PArrayDataTypeDecoder.positionAtArrayElement(PArrayDataTypeDecoder.java:45)
> at
> org.apache.phoenix.expression.function.ArrayIndexFunction.evaluate(ArrayIndexFunction.java:64)
> at
> org.apache.phoenix.util.ExpressionUtil.getConstantExpression(ExpressionUtil.java:72)
> at
> org.apache.phoenix.compile.ExpressionCompiler.visitLeave(ExpressionCompiler.java:348)
> at
> org.apache.phoenix.compile.ProjectionCompiler$SelectClauseVisitor.visitLeave(ProjectionCompiler.java:717)
> at
> org.apache.phoenix.compile.ExpressionCompiler.visitLeave(ExpressionCompiler.java:1)
> at
> org.apache.phoenix.parse.FunctionParseNode.accept(FunctionParseNode.java:87)
> at
> org.apache.phoenix.compile.ProjectionCompiler.compile(ProjectionCompiler.java:425)
> at
> org.apache.phoenix.compile.QueryCompiler.compileSingleFlatQuery(QueryCompiler.java:637)
> at
> org.apache.phoenix.compile.QueryCompiler.compileSingleQuery(QueryCompiler.java:574)
> at
> org.apache.phoenix.compile.QueryCompiler.compileSelect(QueryCompiler.java:203)
> at org.apache.phoenix.compile.QueryCompiler.compile(QueryCompiler.java:157)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$ExecutableSelectStatement.compilePlan(PhoenixStatement.java:497)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$ExecutableSelectStatement.compilePlan(PhoenixStatement.java:1)
> at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:303)
> at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:1)
> at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:291)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:284)
> at
> org.apache.phoenix.jdbc.PhoenixPreparedStatement.executeQuery(PhoenixPreparedStatement.java:193)
> at
> org.apache.phoenix.end2end.Array2IT.testArrayRefToLiteral(Array2IT.java:682)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(Remot
[jira] [Closed] (PHOENIX-5327) PherfMainIT fails with duplicate TABLE/INDEX.
[
https://issues.apache.org/jira/browse/PHOENIX-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swaroopa Kadam closed PHOENIX-5327.
---
bulk closing of jiras after 4.14.3 release
> PherfMainIT fails with duplicate TABLE/INDEX.
> -
>
> Key: PHOENIX-5327
> URL: https://issues.apache.org/jira/browse/PHOENIX-5327
> Project: Phoenix
> Issue Type: Test
>Affects Versions: 4.15.0, 5.1.0
>Reporter: Lars Hofhansl
>Assignee: Viraj Jasani
>Priority: Blocker
> Labels: phoenix-hardening
> Fix For: 4.15.1, 4.14.3, 5.1.1
>
> Attachments: PHOENIX-5327-4.14-HBase-1.3.patch,
> PHOENIX-5327-4.14-HBase-1.4.patch, PHOENIX-5327-4.x-HBase-1.3.patch,
> PHOENIX-5327-4.x-HBase-1.3.patch, PHOENIX-5327-4.x-HBase-1.4.patch,
> PHOENIX-5327-4.x-HBase-1.4.patch, PHOENIX-5327-4.x-HBase-1.5.patch,
> PHOENIX-5327.01.patch, PHOENIX-5327.4.14-HBase-1.3.v2.patch,
> PHOENIX-5327.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {code:java}
> INFO] Running org.apache.phoenix.pherf.PherfMainIT
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 54.221 s <<< FAILURE! - in org.apache.phoenix.pherf.PherfMainIT
> [ERROR] testPherfMain(org.apache.phoenix.pherf.PherfMainIT) Time elapsed:
> 10.455 s <<< ERROR!
> java.util.concurrent.ExecutionException:
> org.apache.phoenix.schema.TableAlreadyExistsException: ERROR 1013 (42M04):
> Table already exists. tableName=PHERF.IDX_DIVISION
> at org.apache.phoenix.pherf.PherfMainIT.testPherfMain(PherfMainIT.java:42)
> Caused by: org.apache.phoenix.schema.TableAlreadyExistsException: ERROR 1013
> (42M04): Table already exists. tableName=PHERF.IDX_DIVISION
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (PHOENIX-5419) Cleanup anonymous class in TracingQueryPlan
[ https://issues.apache.org/jira/browse/PHOENIX-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Jain updated PHOENIX-5419: Attachment: PHOENIX-5419-4.x-HBase-1.3.patch > Cleanup anonymous class in TracingQueryPlan > --- > > Key: PHOENIX-5419 > URL: https://issues.apache.org/jira/browse/PHOENIX-5419 > Project: Phoenix > Issue Type: Sub-task >Reporter: Ankit Jain >Assignee: Ankit Jain >Priority: Minor > Attachments: PHOENIX-5419-4.x-HBase-1.3.patch, PHOENIX-5419.patch, > PHOENIX-5419.v2.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Cleanup anonymous class in TracingQueryPlan -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (PHOENIX-5303) Fix index failures with some versions of HBase.
[
https://issues.apache.org/jira/browse/PHOENIX-5303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swaroopa Kadam closed PHOENIX-5303.
---
bulk closing of jiras after 4.14.3 release
> Fix index failures with some versions of HBase.
> ---
>
> Key: PHOENIX-5303
> URL: https://issues.apache.org/jira/browse/PHOENIX-5303
> Project: Phoenix
> Issue Type: Test
>Affects Versions: 4.15.0, 5.1.0
>Reporter: Lars Hofhansl
>Assignee: Lars Hofhansl
>Priority: Blocker
> Fix For: 4.15.0, 5.1.0, 4.14.3
>
> Attachments: 5303.txt
>
>
> The problem was introduced with HBASE-21158. The fix here works regardless of
> the HBase version.
> This must have started very recently, but it's already past the history of
> the test runs.
> Or perhaps it never works in 4.x-HBase-1.5
> [~apurtell], in case you have any ideas.
> {code:java}
> [INFO] Running
> org.apache.phoenix.hbase.index.covered.TestCoveredColumnIndexCodec
> [ERROR] Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.403
> s <<< FAILURE! - in
> org.apache.phoenix.hbase.index.covered.TestCoveredColumnIndexCodec
> [ERROR]
> testGeneratedIndexUpdates(org.apache.phoenix.hbase.index.covered.TestCoveredColumnIndexCodec)
> Time elapsed: 0.16 s <<< FAILURE!
> java.lang.AssertionError: Had some index updates, though it should have been
> covered by the delete
> at
> org.apache.phoenix.hbase.index.covered.TestCoveredColumnIndexCodec.ensureNoUpdatesWhenCoveredByDelete(TestCoveredColumnIndexCodec.java:242)
> at
> org.apache.phoenix.hbase.index.covered.TestCoveredColumnIndexCodec.testGeneratedIndexUpdates(TestCoveredColumnIndexCodec.java:220)
> {code}
>
> MutableIndexIT fails as well (for non-transactional indexes)
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Closed] (PHOENIX-5383) Metrics for the IndexRegionObserver coprocesor
[ https://issues.apache.org/jira/browse/PHOENIX-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam closed PHOENIX-5383. --- bulk closing of jiras after 4.14.3 release > Metrics for the IndexRegionObserver coprocesor > -- > > Key: PHOENIX-5383 > URL: https://issues.apache.org/jira/browse/PHOENIX-5383 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0, 5.1.0 >Reporter: Priyank Porwal >Assignee: Priyank Porwal >Priority: Major > Fix For: 4.15.0, 5.1.0, 4.14.3 > > Attachments: PHOENIX-5383.4.x-HBase-1.3.v1.patch, > PHOENIX-5383.4.x-HBase-1.3.v1.patch, PHOENIX-5383.master.v1.patch > > Time Spent: 50m > Remaining Estimate: 0h > > Need to track index write failures in phase1 and phase3 after the index > re-design done as part of PHOENIX-5156 and -PHOENIX-5211.- -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (PHOENIX-5441) NPE in phoenix-pherf/ConfigurationParserTest#testConfigReader
[
https://issues.apache.org/jira/browse/PHOENIX-5441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swaroopa Kadam closed PHOENIX-5441.
---
bulk closing of jiras after 4.14.3 release
> NPE in phoenix-pherf/ConfigurationParserTest#testConfigReader
> --
>
> Key: PHOENIX-5441
> URL: https://issues.apache.org/jira/browse/PHOENIX-5441
> Project: Phoenix
> Issue Type: Improvement
>Affects Versions: 4.14.3
>Reporter: Mihir Monani
>Assignee: Mihir Monani
>Priority: Trivial
> Fix For: 4.14.3
>
> Attachments: PHOENIX-5411-4.x-HBase-1.3.patch,
> PHOENIX-5411-4.x-HBase-1.4.patch, PHOENIX-5441.4.14-HBase-1.3.v1.patch,
> PHOENIX-5441.4.14-HBase-1.3.v2.patch
>
>
> NPE is happening because of missing scenario name in phoenix-pherf test
> ConfigurationParserTest#testConfigReader.
>
>
> {code:java}
> java.lang.NullPointerException
> at
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:191)
> at
> org.apache.phoenix.pherf.configuration.Scenario.getName(Scenario.java:168)
> at
> org.apache.phoenix.pherf.configuration.Scenario$JaxbAccessorM_getName_setName_java_lang_String.get(MethodAccessor_Ref.java:56)
> at
> com.sun.xml.bind.v2.runtime.reflect.TransducedAccessor$CompositeTransducedAccessorImpl.print(TransducedAccessor.java:241)
> at
> com.sun.xml.bind.v2.runtime.property.AttributeProperty.serializeAttributes(AttributeProperty.java:101)
> at
> com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeAttributes(ClassBeanInfoImpl.java:360)
> at
> com.sun.xml.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:693)
> at
> com.sun.xml.bind.v2.runtime.property.ArrayElementNodeProperty.serializeItem(ArrayElementNodeProperty.java:69)
> at
> com.sun.xml.bind.v2.runtime.property.ArrayElementProperty.serializeListBody(ArrayElementProperty.java:172)
> at
> com.sun.xml.bind.v2.runtime.property.ArrayERProperty.serializeBody(ArrayERProperty.java:159)
> at
> com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:344)
> at
> com.sun.xml.bind.v2.runtime.XMLSerializer.childAsSoleContent(XMLSerializer.java:597)
> at
> com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeRoot(ClassBeanInfoImpl.java:328)
> at
> com.sun.xml.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:498)
> at
> com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:320)
> at
> com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:249)
> at
> javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:95)
> at
> org.apache.phoenix.pherf.ConfigurationParserTest.writeXML(ConfigurationParserTest.java:239)
> at
> org.apache.phoenix.pherf.ConfigurationParserTest.testConfigReader(ConfigurationParserTest.java:68)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
> at
> org.apache.m
[jira] [Closed] (PHOENIX-5382) Perf improvement with bulk operation over iterations
[ https://issues.apache.org/jira/browse/PHOENIX-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam closed PHOENIX-5382. --- bulk closing of jiras after 4.14.3 release > Perf improvement with bulk operation over iterations > > > Key: PHOENIX-5382 > URL: https://issues.apache.org/jira/browse/PHOENIX-5382 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0, 4.15.1, 4.14.3 >Reporter: Viraj Jasani >Assignee: Viraj Jasani >Priority: Blocker > Fix For: 4.15.0, 5.1.0, 4.14.3 > > Attachments: PHOENIX-5382-4.14-HBase-1.3.patch, > PHOENIX-5382-4.14-HBase-1.3.v2.patch, PHOENIX-5382-4.14-HBase-1.4.patch, > PHOENIX-5382-4.14-HBase-1.4.v2.patch, PHOENIX-5382-4.x-HBase-1.3.patch, > PHOENIX-5382-4.x-HBase-1.3.v2.patch, PHOENIX-5382-4.x-HBase-1.4.patch, > PHOENIX-5382-4.x-HBase-1.4.v2.patch, PHOENIX-5382-4.x-HBase-1.5.patch, > PHOENIX-5382-4.x-HBase-1.5.v2.patch, PHOENIX-5382.patch > > Time Spent: 1h 10m > Remaining Estimate: 0h > > At some places, we are using iteration to add all elements of one collection > to another one. We can use bulk APIs to improve performance -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (PHOENIX-5318) Slots passed to SkipScan filter is incorrect for desc primary keys that are prefixes of each other
[
https://issues.apache.org/jira/browse/PHOENIX-5318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swaroopa Kadam closed PHOENIX-5318.
---
bulk closing of jiras after 4.14.3 release
> Slots passed to SkipScan filter is incorrect for desc primary keys that are
> prefixes of each other
> --
>
> Key: PHOENIX-5318
> URL: https://issues.apache.org/jira/browse/PHOENIX-5318
> Project: Phoenix
> Issue Type: Improvement
>Affects Versions: 4.15.0, 5.1.0, 4.14.3
>Reporter: Thomas D'Silva
>Assignee: Thomas D'Silva
>Priority: Major
> Labels: DESC
> Fix For: 4.15.0, 5.1.0, 4.14.3
>
> Attachments: PHOENIX-5318-4.x-HBase-1.3.patch
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> {code}
> CREATE VIEW IF NOT EXISTS CUSTOM_ENTITY."z01" (COL1 VARCHAR, COL2 VARCHAR,
> COL3 VARCHAR, COL4 VARCHAR CONSTRAINT PK PRIMARY KEY (COL1 DESC, COL2 DESC,
> COL3 DESC, COL4 DESC)) AS SELECT * FROM
> CUSTOM_ENTITY.CUSTOM_ENTITY_DATA_NO_ID WHERE KEY_PREFIX = 'z01';
>
> UPSERT INTO CUSTOM_ENTITY."z01" (COL1, COL2, COL3, COL4) VALUES ('8', 'blah',
> 'blah', 'blah');
> UPSERT INTO CUSTOM_ENTITY."z01" (COL1, COL2, COL3, COL4) VALUES ('6', 'blah',
> 'blah', 'blah');
> UPSERT INTO CUSTOM_ENTITY."z01" (COL1, COL2, COL3, COL4) VALUES ('23',
> 'blah', 'blah', 'blah');
> UPSERT INTO CUSTOM_ENTITY."z01" (COL1, COL2, COL3, COL4) VALUES ('17',
> 'blah', 'blah', 'blah');
>
> SELECT COL1, COL2, COL3, COL4 FROM CUSTOM_ENTITY."z01" WHERE COL4='blah' AND
> (COL1='1' OR COL1='2' OR COL1='3' OR COL1='4' OR COL1='5' OR COL1='6' OR
> COL1='8' OR COL1='17' OR COL1='12' OR COL1='23') AND COL3='blah'
>
> +---+---+---+---+
> | COL1 | COL2 | COL3 | COL4 |
> +---+---+---+---+
> | 8 | blah | blah | blah |
> | 6 | blah | blah | blah |
> +---+---+---+---+
>
> SELECT COL1, COL2, COL3, COL4 FROM CUSTOM_ENTITY."z01" WHERE COL4='blah' AND
> (COL1='6'OR COL1='8' OR COL1='17' OR COL1='12' OR COL1='23') AND COL3='blah'
>
> +---+---+---+---+
> | COL1 | COL2 | COL3 | COL4 |
> +---+---+---+---+
> | 8 | blah | blah | blah |
> | 6 | blah | blah | blah |
> | 23 | blah | blah | blah |
> | 17 | blah | blah | blah |
> +---+---+---+---
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Closed] (PHOENIX-5358) Metrics for the GlobalIndexChecker coprocessor
[ https://issues.apache.org/jira/browse/PHOENIX-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam closed PHOENIX-5358. --- bulk closing of jiras after 4.14.3 release > Metrics for the GlobalIndexChecker coprocessor > -- > > Key: PHOENIX-5358 > URL: https://issues.apache.org/jira/browse/PHOENIX-5358 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.13.1, 5.0.0, 4.15.0, 4.14.2 >Reporter: Kadir OZDEMIR >Assignee: Priyank Porwal >Priority: Major > Fix For: 4.15.0, 5.1.0, 4.14.3 > > Attachments: PHOENIX-5358.4.x-HBase-1.3.v2.patch, > PHOENIX-5358.master.v4.patch > > Time Spent: 2.5h > Remaining Estimate: 0h > > The GlobalIndexChecker coprocessor is responsible for checking if an index > row is "verified", that is, has completed its most recent two-phase write > operation, during scans. If the row is not verified then the coprocessor > rebuilds the row using a read-repair technique. The read-repair operations > should be rare but add extra latency on the scan operations. We need to know > how many read-repair operations happen and how long they take. Thus, we need > metrics on them. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (PHOENIX-5228) use slf4j for logging in phoenix project
[
https://issues.apache.org/jira/browse/PHOENIX-5228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swaroopa Kadam closed PHOENIX-5228.
---
bulk closing of jiras after 4.14.3 release
> use slf4j for logging in phoenix project
>
>
> Key: PHOENIX-5228
> URL: https://issues.apache.org/jira/browse/PHOENIX-5228
> Project: Phoenix
> Issue Type: Improvement
>Affects Versions: 4.14.1, 5.1.0
>Reporter: Mihir Monani
>Assignee: Xinyi Yan
>Priority: Trivial
> Labels: SFDC
> Fix For: 4.15.0, 5.1.0, 4.14.3
>
> Attachments: PHOENIX-5228-4.x-HBase-1.3.patch,
> PHOENIX-5228-4.x-HBase-1.4.patch, PHOENIX-5228-4.x-HBase-1.5.patch,
> PHOENIX-5228-FIX-4.x-HBase-1.3.patch, PHOENIX-5228-FIX-4.x-HBase-1.4.patch,
> PHOENIX-5228-FIX-4.x-HBase-1.5.patch, PHOENIX-5228-FIX-master.patch,
> PHOENIX-5228-addendum-4.14-HBase-1.3.patch,
> PHOENIX-5228-addendum-4.14-HBase-1.4.patch, PHOENIX-5228.patch
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> It would be good to use slf4j for logging in phoenix project. Here is list of
> files where doesn't use slf4j.
> phoenix-core :-
> {noformat}
> WALRecoveryRegionPostOpenIT.java
> WALReplayWithIndexWritesAndCompressedWALIT.java
> BasePermissionsIT.java
> ChangePermissionsIT.java
> IndexRebuildIncrementDisableCountIT.java
> InvalidIndexStateClientSideIT.java
> MutableIndexReplicationIT.java
> FailForUnsupportedHBaseVersionsIT.java
> SecureUserConnectionsIT.java
> PhoenixMetricsIT.java
> BaseTracingTestIT.java
> PhoenixTracingEndToEndIT.java
> PhoenixRpcSchedulerFactory.java
> IndexHalfStoreFileReaderGenerator.java
> BinaryCompatibleBaseDecoder.java
> ServerCacheClient.java
> CallRunner.java
> MetaDataRegionObserver.java
> PhoenixAccessController.java
> ScanRegionObserver.java
> TaskRegionObserver.java
> DropChildViewsTask.java
> IndexRebuildTask.java
> BaseQueryPlan.java
> HashJoinPlan.java
> CollationKeyFunction.java
> Indexer.java
> LockManager.java
> BaseIndexBuilder.java
> IndexBuildManager.java
> NonTxIndexBuilder.java
> IndexMemStore.java
> BaseTaskRunner.java
> QuickFailingTaskRunner.java
> TaskBatch.java
> ThreadPoolBuilder.java
> ThreadPoolManager.java
> IndexManagementUtil.java
> IndexWriter.java
> IndexWriterUtils.java
> KillServerOnFailurePolicy.java
> ParallelWriterIndexCommitter.java
> RecoveryIndexWriter.java
> TrackingParallelWriterIndexCommitter.java
> PhoenixIndexFailurePolicy.java
> PhoenixTransactionalIndexer.java
> SnapshotScanner.java
> PhoenixEmbeddedDriver.java
> PhoenixResultSet.java
> QueryLogger.java
> QueryLoggerDisruptor.java
> TableLogWriter.java
> PhoenixInputFormat.java
> PhoenixOutputFormat.java
> PhoenixRecordReader.java
> PhoenixRecordWriter.java
> PhoenixServerBuildIndexInputFormat.java
> PhoenixMRJobSubmitter.java
> PhoenixConfigurationUtil.java
> Metrics.java
> DefaultStatisticsCollector.java
> StatisticsScanner.java
> PhoenixMetricsSink.java
> TraceReader.java
> TraceSpanReceiver.java
> TraceWriter.java
> Tracing.java
> EquiDepthStreamHistogram.java
> PhoenixMRJobUtil.java
> QueryUtil.java
> ServerUtil.java
> ZKBasedMasterElectionUtil.java
> IndexTestingUtils.java
> StubAbortable.java
> TestIndexWriter.java
> TestParalleIndexWriter.java
> TestParalleWriterIndexCommitter.java
> TestWALRecoveryCaching.java
> LoggingSink.java
> ParameterizedPhoenixCanaryToolIT.java
> CoprocessorHConnectionTableFactoryTest.java
> TestUtil.java{noformat}
> phoenix-tracing-webapp :-
> {noformat}
> org/apache/phoenix/tracingwebapp/http/Main.java
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Closed] (PHOENIX-5316) Use callable instead of runnable so that Pherf exceptions cause tests to fail
[ https://issues.apache.org/jira/browse/PHOENIX-5316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam closed PHOENIX-5316. --- bulk closing of jiras after 4.14.3 release > Use callable instead of runnable so that Pherf exceptions cause tests to fail > - > > Key: PHOENIX-5316 > URL: https://issues.apache.org/jira/browse/PHOENIX-5316 > Project: Phoenix > Issue Type: Improvement >Reporter: Thomas D'Silva >Assignee: Thomas D'Silva >Priority: Major > Labels: pherf > Fix For: 4.15.0, 5.1.0, 4.14.3 > > Attachments: PHOENIX-5316-4.x-HBase-1.3.patch > > Time Spent: 40m > Remaining Estimate: 0h > > Also add support for BIGINT and TINYINT. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (PHOENIX-5343) OrphanViewTool should not check Index Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam closed PHOENIX-5343. --- bulk closing of jiras after 4.14.3 release > OrphanViewTool should not check Index Tables > > > Key: PHOENIX-5343 > URL: https://issues.apache.org/jira/browse/PHOENIX-5343 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.14.0, 5.0.0, 4.15.0 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Fix For: 4.15.0, 5.1.0, 4.14.3 > > Attachments: PHOENIX-5343.master.001.patch, > PHOENIX-5343.master.002.patch > > > OrphanViewTool checks the integrity of a view tree rooted at a table. The set > of candidate root tables should not include Index Tables. OrphanViewTool > should only consider tables of type PTableType.TABLE. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (PHOENIX-5333) A tool to upgrade existing tables/indexes to use self-consistent global indexes design
[ https://issues.apache.org/jira/browse/PHOENIX-5333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam closed PHOENIX-5333. --- bulk closing of jiras after 4.14.3 release > A tool to upgrade existing tables/indexes to use self-consistent global > indexes design > -- > > Key: PHOENIX-5333 > URL: https://issues.apache.org/jira/browse/PHOENIX-5333 > Project: Phoenix > Issue Type: Improvement >Reporter: Swaroopa Kadam >Assignee: Swaroopa Kadam >Priority: Major > Fix For: 4.15.0, 5.1.0, 4.14.3 > > Attachments: PHOENIX-5333.4.x-HBase-1.3.v1.patch, > PHOENIX-5333.4.x-HBase-1.3.v2.patch, PHOENIX-5333.master.v1.patch, > PHOENIX-5333.master.v2.patch, PHOENIX-5333.master.v3.patch, > PHOENIX-5333.master.v4.patch, PHOENIX-5333.master.v5.patch, > PHOENIX-5333.master.v6.patch > > Time Spent: 20h 20m > Remaining Estimate: 0h > > A tool to upgrade existing tables/indexes to use self-consistent global > indexes design in PHOENIX-5156 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (PHOENIX-5401) Error in running apache.phoenix.mapreduce.index.automation.PhoenixMRJobSubmitter
[
https://issues.apache.org/jira/browse/PHOENIX-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swaroopa Kadam closed PHOENIX-5401.
---
bulk closing of jiras after 4.14.3 release
> Error in running
> apache.phoenix.mapreduce.index.automation.PhoenixMRJobSubmitter
>
>
> Key: PHOENIX-5401
> URL: https://issues.apache.org/jira/browse/PHOENIX-5401
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.14.1
>Reporter: Ashutosh Parekh
>Assignee: Kadir OZDEMIR
>Priority: Major
> Fix For: 4.15.0, 5.1.0, 4.14.3
>
> Attachments: PHOENIX-5401.master.001.patch, yarnIssueIT.java
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Initially, the following query is executed:
>
> {code:java}
> CREATE TABLE IF NOT EXISTS us_population (
> state CHAR(2) NOT NULL,
> city VARCHAR NOT NULL,
> population BIGINT,
> CONSTRAINT my_pk PRIMARY KEY (state, city)) COLUMN_ENCODED_BYTES=0;
> UPSERT INTO us_population VALUES('NY','New York',8143197);
> UPSERT INTO us_population VALUES('CA','Los Angeles',3844829);
> UPSERT INTO us_population VALUES('IL','Chicago',2842518);
> UPSERT INTO us_population VALUES('TX','Houston',2016582);
> UPSERT INTO us_population VALUES('PA','Philadelphia',1463281);
> UPSERT INTO us_population VALUES('AZ','Phoenix',1461575);
> UPSERT INTO us_population VALUES('TX','San Antonio',1256509);
> UPSERT INTO us_population VALUES('CA','San Diego',1255540);
> UPSERT INTO us_population VALUES('TX','Dallas',1213825);
> UPSERT INTO us_population VALUES('CA','San Jose',912332);
> CREATE VIEW us_population_global_view (name VARCHAR,
> age BIGINT) AS
> SELECT * FROM us_population
> WHERE state = 'CA';
> CREATE INDEX us_population_gv_gi_1 ON us_population_global_view(age) include
> (city) async;
> {code}
>
> Then,
> {code:java}
> org.apache.phoenix.mapreduce.index.automation.PhoenixMRJobSubmitter{code}
> is run.
> The YARN application logs then show the following error:
> {code:java}
> 2019-07-16 19:40:50,397 ERROR [main]
> org.apache.phoenix.mapreduce.PhoenixServerBuildIndexInputFormat: Failed to
> get the query plan with error [ERROR 534 (42911): If both specified, values
> of CURRENT_SCN and BUILD_INDEX_AT must be equal.]
> 2019-07-16 19:40:50,398 WARN [main] org.apache.hadoop.mapred.YarnChild:
> Exception running child : java.lang.RuntimeException: java.sql.SQLException:
> ERROR 534 (42911): If both specified, values of CURRENT_SCN and
> BUILD_INDEX_AT must be equal.
> at
> org.apache.phoenix.mapreduce.PhoenixServerBuildIndexInputFormat.getQueryPlan(PhoenixServerBuildIndexInputFormat.java:108)
> at
> org.apache.phoenix.mapreduce.PhoenixInputFormat.createRecordReader(PhoenixInputFormat.java:75)
> at
> org.apache.hadoop.mapred.MapTask$NewTrackingRecordReader.(MapTask.java:515)
> at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:758)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341)
> at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:170)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1760)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:164)
> Caused by: java.sql.SQLException: ERROR 534 (42911): If both specified,
> values of CURRENT_SCN and BUILD_INDEX_AT must be equal.
> at
> org.apache.phoenix.exception.SQLExceptionCode$Factory$1.newException(SQLExceptionCode.java:494)
> at
> org.apache.phoenix.exception.SQLExceptionInfo.buildException(SQLExceptionInfo.java:150)
> at
> org.apache.phoenix.jdbc.PhoenixConnection.checkScnAndBuildIndexAtEquality(PhoenixConnection.java:415)
> at
> org.apache.phoenix.jdbc.PhoenixConnection.(PhoenixConnection.java:285)
> at
> org.apache.phoenix.jdbc.PhoenixConnection.(PhoenixConnection.java:229)
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl$12.call(ConnectionQueryServicesImpl.java:2533)
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl$12.call(ConnectionQueryServicesImpl.java:2499)
> at
> org.apache.phoenix.util.PhoenixContextExecutor.call(PhoenixContextExecutor.java:76)
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl.init(ConnectionQueryServicesImpl.java:2499)
> at
> org.apache.phoenix.jdbc.PhoenixDriver.getConnectionQueryServices(PhoenixDriver.java:255)
> at
> org.apache.phoenix.jdbc.PhoenixEmbeddedDriver.createConnection(PhoenixEmbeddedDriver.java:147)
> at org.apache.phoenix.jdbc.PhoenixDriver.connect(PhoenixDriver.java:221)
> at java.sql.DriverManager.getConnection(DriverManager.java:664)
> at java.sql.DriverManager.getConnection(DriverManager.java:208)
> at
> org.apache.phoenix.mapreduce.util.ConnectionUtil.getConnection(Connecti
[jira] [Closed] (PHOENIX-5418) ResultTest failure in phoenix-pherf
[ https://issues.apache.org/jira/browse/PHOENIX-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam closed PHOENIX-5418. --- bulk closing of jiras after 4.14.3 release > ResultTest failure in phoenix-pherf > > > Key: PHOENIX-5418 > URL: https://issues.apache.org/jira/browse/PHOENIX-5418 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.14.2 >Reporter: Swaroopa Kadam >Assignee: Viraj Jasani >Priority: Blocker > Fix For: 4.14.3 > > Attachments: PHOENIX-5418-4.14-HBase-1.3.patch, > PHOENIX-5418-4.14-HBase-1.4.patch > > > ResultTest fails with NPE in 4.14 branch. > > `java.lang.NullPointerException > at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:191) > at org.apache.phoenix.pherf.configuration.Scenario.getName(Scenario.java:168) > at > org.apache.phoenix.pherf.configuration.Scenario$JaxbAccessorM_getName_setName_java_lang_String.get(MethodAccessor_Ref.java:56) > at > com.sun.xml.bind.v2.runtime.reflect.TransducedAccessor$CompositeTransducedAccessorImpl.print(TransducedAccessor.java:241) > at > com.sun.xml.bind.v2.runtime.property.AttributeProperty.serializeAttributes(AttributeProperty.java:101) > at > com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeAttributes(ClassBeanInfoImpl.java:360) > at > com.sun.xml.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:693) > at > com.sun.xml.bind.v2.runtime.property.ArrayElementNodeProperty.serializeItem(ArrayElementNodeProperty.java:69) > at > com.sun.xml.bind.v2.runtime.property.ArrayElementProperty.serializeListBody(ArrayElementProperty.java:172) > at > com.sun.xml.bind.v2.runtime.property.ArrayERProperty.serializeBody(ArrayERProperty.java:159) > at > com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:344) > at > com.sun.xml.bind.v2.runtime.XMLSerializer.childAsSoleContent(XMLSerializer.java:597) > at > com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeRoot(ClassBeanInfoImpl.java:328) > at > com.sun.xml.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:498) > at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:320) > at > com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:249) > at > javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:95) > at > org.apache.phoenix.pherf.result.impl.XMLResultHandler.write(XMLResultHandler.java:54) > at org.apache.phoenix.pherf.result.ResultUtil.write(ResultUtil.java:142) > at > org.apache.phoenix.pherf.result.ResultManager.write(ResultManager.java:101) > at org.apache.phoenix.pherf.result.ResultManager.write(ResultManager.java:87) > at org.apache.phoenix.pherf.ResultTest.testResult(ResultTest.java:120) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at > com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68) > at > com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47) > at > com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242) > at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70) > Process finished with exit code 255` > -- This message was sent by Atlassian Ji
[jira] [Closed] (PHOENIX-5313) All mappers grab all RegionLocations from .META
[
https://issues.apache.org/jira/browse/PHOENIX-5313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swaroopa Kadam closed PHOENIX-5313.
---
bulk closing of jiras after 4.14.3 release
> All mappers grab all RegionLocations from .META
> ---
>
> Key: PHOENIX-5313
> URL: https://issues.apache.org/jira/browse/PHOENIX-5313
> Project: Phoenix
> Issue Type: Bug
>Reporter: Geoffrey Jacoby
>Assignee: Chinmay Kulkarni
>Priority: Major
> Labels: phoenix-hardening
> Fix For: 4.15.0, 5.1.0, 4.14.3
>
> Attachments: PHOENIX-5313-4.x-HBase-1.3.patch, PHOENIX-5313-v1.patch
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Phoenix's MapReduce integration lives in PhoenixInputFormat. It implements
> getSplits by calculating a QueryPlan for the provided SELECT query, and each
> split gets a mapper. As part of this QueryPlan generation, we grab all
> RegionLocations from .META
> In PhoenixInputFormat:getQueryPlan:
> {code:java}
> // Initialize the query plan so it sets up the parallel scans
> queryPlan.iterator(MapReduceParallelScanGrouper.getInstance());
> {code}
> In MapReduceParallelScanGrouper.getRegionBoundaries()
> {code:java}
> return
> context.getConnection().getQueryServices().getAllTableRegions(tableName);
> {code}
> This is fine.
> Unfortunately, each mapper Task spawned by the job will go through this
> _same_ exercise. It will pass a MapReduceParallelScanGrouper to
> queryPlan.iterator(), which I believe is eventually causing
> getRegionBoundaries to get called when the scans are initialized in the
> result iterator.
> Since HBase 1.x and up got rid of .META prefetching and caching within the
> HBase client, that means that not only will each _Job_ make potentially
> thousands of calls to .META, potentially thousands of _Tasks_ will each make
> potentially thousands of calls to .META.
> We should get a QueryPlan and setup the scans without having to read all
> RegionLocations, either by using the mapper's internal knowledge of its split
> key range, or by serializing the query plan from the client and sending it to
> the mapper tasks for use there.
> Note that MapReduce tasks over snapshots are not affected by this, because
> region locations are stored in the snapshot manifest.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Closed] (PHOENIX-5380) Provide class check for equals() in Scenario and Column classes
[ https://issues.apache.org/jira/browse/PHOENIX-5380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam closed PHOENIX-5380. --- bulk closing of jiras after 4.14.3 release > Provide class check for equals() in Scenario and Column classes > --- > > Key: PHOENIX-5380 > URL: https://issues.apache.org/jira/browse/PHOENIX-5380 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.15.0, 4.15.1, 4.14.3 >Reporter: Viraj Jasani >Assignee: Viraj Jasani >Priority: Major > Fix For: 4.15.0, 4.15.1, 4.14.3 > > Time Spent: 0.5h > Remaining Estimate: 0h > > equals() in Scenario and Column classes is missing class check. Hence, it has > possibility of causing ClassCastException -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (PHOENIX-5379) Avoid possible NPE while closing CSVParser
[ https://issues.apache.org/jira/browse/PHOENIX-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam closed PHOENIX-5379. --- bulk closing of jiras after 4.14.3 release > Avoid possible NPE while closing CSVParser > -- > > Key: PHOENIX-5379 > URL: https://issues.apache.org/jira/browse/PHOENIX-5379 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.15.0, 4.15.1, 4.14.3 >Reporter: Viraj Jasani >Assignee: Viraj Jasani >Priority: Major > Fix For: 4.15.0, 4.15.1, 4.14.3 > > Attachments: PHOENIX-5379.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > CSVFileResultHandler closes the parser which could cause NPE if CSVParser > parse cause IOException. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (PHOENIX-5415) NPE in getting conf from addHbaseResources in IndexUpgradeTool
[ https://issues.apache.org/jira/browse/PHOENIX-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam closed PHOENIX-5415. --- bulk closing of jiras after 4.14.3 release > NPE in getting conf from addHbaseResources in IndexUpgradeTool > -- > > Key: PHOENIX-5415 > URL: https://issues.apache.org/jira/browse/PHOENIX-5415 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.15.0, 5.1.0, 4.14.3 >Reporter: Swaroopa Kadam >Assignee: Swaroopa Kadam >Priority: Blocker > Fix For: 4.15.0, 5.1.0, 4.14.3 > > Attachments: PHOENIX-5415.4.14-HBase-1.3.v1.patch, > PHOENIX-5415.4.14-HBase-1.3.v2.patch, PHOENIX-5415.4.x-HBase-1.3.v1.patch, > PHOENIX-5415.master.v1.patch > > Time Spent: 2h 50m > Remaining Estimate: 0h > > The tool doesnt implement Tool class to load the resources correctly. > Getting following exception. > Exception in thread “main” java.lang.NullPointerException > at > org.apache.hadoop.hbase.HBaseConfiguration.addHbaseResources(HBaseConfiguration.java:78) > at > org.apache.phoenix.mapreduce.index.IndexUpgradeTool.executeTool(IndexUpgradeTool.java:298) > at > org.apache.phoenix.mapreduce.index.IndexUpgradeTool.main(IndexUpgradeTool.java:160) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (PHOENIX-5387) Remove or document the dependecy of com.github.stefanbirkn from Phoenix-pherf
[ https://issues.apache.org/jira/browse/PHOENIX-5387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam closed PHOENIX-5387. --- bulk closing of jiras after 4.14.3 release > Remove or document the dependecy of com.github.stefanbirkn from Phoenix-pherf > - > > Key: PHOENIX-5387 > URL: https://issues.apache.org/jira/browse/PHOENIX-5387 > Project: Phoenix > Issue Type: Bug >Reporter: Swaroopa Kadam >Assignee: Geoffrey Jacoby >Priority: Blocker > Fix For: 4.15.0, 5.1.0, 4.14.3 > > Attachments: PHOENIX-5387.patch > > Time Spent: 20m > Remaining Estimate: 0h > > It uses the CPL 1.0 which is an Apace Category B license. According to the > Apache Foundation, these can be used in Apache projects as binary > dependencies so long as they are documented. > See [here|https://www.apache.org/legal/resolved.html#category-b] -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (PHOENIX-5391) MetadataClient - TenantId Map is not correctly updated with list of Table Refs
[ https://issues.apache.org/jira/browse/PHOENIX-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam closed PHOENIX-5391. --- bulk closing of jiras after 4.14.3 release > MetadataClient - TenantId Map is not correctly updated with list of Table Refs > -- > > Key: PHOENIX-5391 > URL: https://issues.apache.org/jira/browse/PHOENIX-5391 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.15.0, 5.1.0, 4.14.3 >Reporter: Viraj Jasani >Assignee: Viraj Jasani >Priority: Major > Fix For: 4.15.0, 5.1.0, 4.14.3 > > Attachments: PHOENIX-5391-4.14-HBase-1.3.patch, > PHOENIX-5391-4.14-HBase-1.4.patch, PHOENIX-5391-4.x-HBase-1.3.patch, > PHOENIX-5391-4.x-HBase-1.4.patch, PHOENIX-5391-4.x-HBase-1.5.patch, > PHOENIX-5391-master.patch > > Time Spent: 2h > Remaining Estimate: 0h > > While dropping column in MetaDataClient, we drop all tenant-specific indexes. > However, tenant specific index map is not correctly updated with list of > index tables as map.contains() refer to different key type -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (PHOENIX-5385) GlobalIndexChecker coproc doesn't load on view indexes
[ https://issues.apache.org/jira/browse/PHOENIX-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam closed PHOENIX-5385. --- bulk closing of jiras after 4.14.3 release > GlobalIndexChecker coproc doesn't load on view indexes > -- > > Key: PHOENIX-5385 > URL: https://issues.apache.org/jira/browse/PHOENIX-5385 > Project: Phoenix > Issue Type: Bug >Reporter: Swaroopa Kadam >Assignee: Swaroopa Kadam >Priority: Blocker > Labels: BLOCKER > Fix For: 4.15.0, 5.1.0, 4.14.3 > > Attachments: PHOENIX-5385.4.14-HBase-1.3.patch, > PHOENIX-5385.4.14-HBase-1.3.v1.patch, PHOENIX-5385.4.x-HBase-1.3.v1.patch, > PHOENIX-5385.4.x-HBase-1.3.v10.patch, PHOENIX-5385.4.x-HBase-1.3.v11.patch, > PHOENIX-5385.4.x-HBase-1.3.v2.patch, PHOENIX-5385.4.x-HBase-1.3.v3.patch, > PHOENIX-5385.4.x-HBase-1.3.v4.patch, PHOENIX-5385.4.x-HBase-1.3.v5.patch, > PHOENIX-5385.4.x-HBase-1.3.v6.patch, PHOENIX-5385.4.x-HBase-1.3.v7.patch, > PHOENIX-5385.4.x-HBase-1.3.v8.patch, PHOENIX-5385.4.x-HBase-1.3.v9.patch, > PHOENIX-5385.4.x-hbase-1.3.v1.patch, PHOENIX-5385.master.v2.patch, > PHOENIX-5385.master.v3.patch, PHOENIX-5385.master.v4.patch, > PHOENIX-5385.master.v5.patch, PHOENIX-5385.master.v6.patch, > PHOENIX-5385.master.v7.patch, PHOENIX-5385.master.v8.patch, > PHOENIX-5385.master.v9.patch > > Time Spent: 4h 20m > Remaining Estimate: 0h > > As found during the dev of IndexUpgradeTool, ensureViewIndexesTableCreated > considers view index table as type TABLE and hence doesn't load > IndexCheckerCorpocessor on it. > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (PHOENIX-5302) Different isNamespaceMappingEnabled for server / client causes TableNotFoundException
[
https://issues.apache.org/jira/browse/PHOENIX-5302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swaroopa Kadam closed PHOENIX-5302.
---
bulk closing of jiras after 4.14.3 release
> Different isNamespaceMappingEnabled for server / client causes
> TableNotFoundException
> -
>
> Key: PHOENIX-5302
> URL: https://issues.apache.org/jira/browse/PHOENIX-5302
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.14.2
>Reporter: Vincent Poon
>Assignee: Chinmay Kulkarni
>Priority: Major
> Fix For: 4.15.0, 5.1.0, 4.14.3
>
> Attachments: PHOENIX-5302-4.14-HBase-1.3-v1.patch,
> PHOENIX-5302-4.14-HBase-1.3-v3.patch, PHOENIX-5302-master.patch,
> Phoenix-5302-4.x-HBase-1.3-v1.patch
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Scenario:
> 1) Fresh cluster start with server isNamespaceMappingEnabled=true.
> 2) Client connects with isNamespaceMappingEnabled=false. Expected exception
> thrown ("Inconsistent namespace mapping")
> 3) Client connects with isNamespaceMappingEnabled=true. Exception: "Table
> undefined. tableName=SYSTEM.CATALOG"
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Closed] (PHOENIX-5300) NoopStatisticsCollector shouldn't scan any rows.
[
https://issues.apache.org/jira/browse/PHOENIX-5300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swaroopa Kadam closed PHOENIX-5300.
---
bulk closing of jiras after 4.14.3 release
> NoopStatisticsCollector shouldn't scan any rows.
>
>
> Key: PHOENIX-5300
> URL: https://issues.apache.org/jira/browse/PHOENIX-5300
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.14.0, 4.13.1
>Reporter: Rushabh S Shah
>Assignee: Rushabh S Shah
>Priority: Major
> Fix For: 4.14.3
>
> Attachments: PHOENIX-5300-4.14-HBase-1.4.patch,
> PHOENIX-5300-4.14-HBase-1.4.patch
>
>
> Today if we disable calculation of stats via
> {{phoenix.stats.collection.enabled}} property, it creates
> {{NoopStatisticsCollector}}. If someone calls "UPDATE STATISTICS
> ", it will create NoopStatisticsCollector, scan the whole table
> and does nothing. This is fixed in 4.15 via PHOENIX-4009. If we don't want to
> backport PHOENIX-4009, we can fix this bug just in 4.14
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Closed] (PHOENIX-5275) Remove accidental imports from curator-client-2.12.0
[ https://issues.apache.org/jira/browse/PHOENIX-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam closed PHOENIX-5275. --- bulk closing of jiras after 4.14.3 release > Remove accidental imports from curator-client-2.12.0 > > > Key: PHOENIX-5275 > URL: https://issues.apache.org/jira/browse/PHOENIX-5275 > Project: Phoenix > Issue Type: Bug >Reporter: Jacob Isaac >Assignee: William Shen >Priority: Minor > Fix For: 4.15.0, 5.1.0, 4.14.3 > > Attachments: PHOENIX-5275.4.14-HBase-1.3.v1.patch, > PHOENIX-5275.4.x-HBase-1.3.v1.patch, PHOENIX-5275.master.v1.patch, > PHOENIX-5275.master.v2.patch > > > The following imports > import org.apache.curator.shaded.com.google.common.* > were accidentally introduced in > phoenix-core/src/test/java/org/apache/phoenix/query/QueryServicesTestImpl.java > phoenix-core/src/it/java/org/apache/phoenix/end2end/UpgradeIT.java > phoenix-core/src/test/java/org/apache/phoenix/compile/WhereOptimizerTest.java -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (PHOENIX-5221) Phoenix Kerberos Integration tests failure on Redhat Linux
[ https://issues.apache.org/jira/browse/PHOENIX-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam closed PHOENIX-5221. --- bulk closing of jiras after 4.14.3 release > Phoenix Kerberos Integration tests failure on Redhat Linux > -- > > Key: PHOENIX-5221 > URL: https://issues.apache.org/jira/browse/PHOENIX-5221 > Project: Phoenix > Issue Type: Bug > Environment: Redhat / Centos Linux >Reporter: Mehdi Salarkia >Assignee: Mehdi Salarkia >Priority: Blocker > Fix For: 4.15.0, queryserver-1.0.0, 4.14.3 > > Attachments: PHOENIX-5221.4.14-HBase-1.4.v1.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > Due to this bug https://bugzilla.redhat.com/show_bug.cgi?id=668830 > We need to use `localhost.localdomain` when running these tests on Jenkins > (Centos) > but for Mac OS it should be `localhost` to pass. > The reason is kerberos principals in this tests are looked up from /etc/hosts > and 127.0.0.1 is resolved to `localhost.localdomain` rather than `localhost` > on Redhat > KDC sees `localhost` != `localhost.localdomain` and as the result test fails > with authentication error. > It's also important to note these principals are shared between HDFs and > HBase in this mini HBase cluster. > Some more reading https://access.redhat.com/solutions/57330 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (PHOENIX-5419) Cleanup anonymous class in TracingQueryPlan
[ https://issues.apache.org/jira/browse/PHOENIX-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Jain updated PHOENIX-5419: Attachment: (was: PHOENIX-5419-4.x-HBase-1.3.patch) > Cleanup anonymous class in TracingQueryPlan > --- > > Key: PHOENIX-5419 > URL: https://issues.apache.org/jira/browse/PHOENIX-5419 > Project: Phoenix > Issue Type: Sub-task >Reporter: Ankit Jain >Assignee: Ankit Jain >Priority: Minor > Attachments: PHOENIX-5419.patch, PHOENIX-5419.v2.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Cleanup anonymous class in TracingQueryPlan -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (PHOENIX-5211) Consistent Immutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam closed PHOENIX-5211. --- bulk closing of jiras after 4.14.3 release > Consistent Immutable Global Indexes for Non-Transactional Tables > > > Key: PHOENIX-5211 > URL: https://issues.apache.org/jira/browse/PHOENIX-5211 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Gokcen Iskender >Priority: Major > Fix For: 4.15.0, 5.1.0, 4.14.3 > > Attachments: PHOENIX-5211.4.14-HBase-1.3.001.patch, > PHOENIX-5211.4.x-HBase-1.3.001.patch, PHOENIX-5211.4.x-HBase-1.3.002.patch, > PHOENIX-5211.master.002.patch, PHOENIX-5211.master.003.patch, > PHOENIX-5211.master.004.patch, PHOENIX-5211.patch > > Time Spent: 11h 40m > Remaining Estimate: 0h > > Without transactional tables, the immutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent immutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (PHOENIX-5156) Consistent Mutable Global Indexes for Non-Transactional Tables
[ https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam closed PHOENIX-5156. --- bulk closing of jiras after 4.14.3 release > Consistent Mutable Global Indexes for Non-Transactional Tables > -- > > Key: PHOENIX-5156 > URL: https://issues.apache.org/jira/browse/PHOENIX-5156 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1 >Reporter: Kadir OZDEMIR >Assignee: Kadir OZDEMIR >Priority: Major > Fix For: 4.15.0, 5.1.0, 4.14.3 > > Attachments: PHOENIX-5156.4.x-HBase-1.4.001.patch, > PHOENIX-5156.4.x-HBase-1.4.002.patch, PHOENIX-5156.4.x-HBase-1.4.005.patch, > PHOENIX-5156.master.001.patch, PHOENIX-5156.master.002.patch, > PHOENIX-5156.master.003.patch, PHOENIX-5156.master.004.patch, > PHOENIX-5156.master.005.patch, PHOENIX-5156.master.006.patch, > PHOENIX-5156.master.007.patch, PHOENIX-5156.master.008.patch, > PHOENIX-5156.master.009.patch, PHOENIX-5156.master.010.patch, > PHOENIX-5156.master.011.patch, PHOENIX-5156.master.012.patch, > PHOENIX-5156.master.013.patch, PHOENIX-5156.master.014.patch, > PHOENIX-5156.master.015.patch, PHOENIX-5156.master.016.patch, > PHOENIX-5156.master.017.patch, PHOENIX-5156.master.019.patch, > PHOENIX-5156.master.021.patch, PHOENIX-5156.master.022.patch > > Time Spent: 31h 10m > Remaining Estimate: 0h > > Without transactional tables, the mutable global indexes can get easily out > of sync with their data tables in Phoenix. Transactional tables require a > separate transaction manager, have some restrictions and performance > penalties. This issue is to have consistent mutable global indexes without > the need for using transactional tables. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (PHOENIX-5122) PHOENIX-4322 breaks client backward compatibility
[
https://issues.apache.org/jira/browse/PHOENIX-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swaroopa Kadam closed PHOENIX-5122.
---
bulk closing of jiras after 4.14.3 release
> PHOENIX-4322 breaks client backward compatibility
> -
>
> Key: PHOENIX-5122
> URL: https://issues.apache.org/jira/browse/PHOENIX-5122
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.13.0
>Reporter: Jacob Isaac
>Assignee: Jacob Isaac
>Priority: Blocker
> Fix For: 4.15.0, 5.1.0, 4.14.3
>
> Attachments: PHOENIX-5122-4.x-HBase-1.3.patch,
> PHOENIX-5122-4.x-HBase-1.3_addendum_v1.patch,
> PHOENIX-5122-addendum-tests.zip, PHOENIX-5122.patch, Screen Shot 2019-03-04
> at 6.17.42 PM.png, Screen Shot 2019-03-04 at 6.21.10 PM.png
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Scenario :
> *4.13 client -> 4.14.1 server*
> {noformat}
> Connected to: Phoenix (version 4.13)
> Driver: PhoenixEmbeddedDriver (version 4.13)
> Autocommit status: true
> Transaction isolation: TRANSACTION_READ_COMMITTED
> Building list of tables and columns for tab-completion (set fastconnect to
> true to skip)...
> 135/135 (100%) Done
> Done
> sqlline version 1.1.9
> 0: jdbc:phoenix:localhost>
> 0: jdbc:phoenix:localhost>
> 0: jdbc:phoenix:localhost> CREATE table P_T02 (oid VARCHAR NOT NULL, code
> VARCHAR NOT NULL constraint pk primary key (oid DESC, code DESC));
> No rows affected (1.31 seconds)
> 0: jdbc:phoenix:localhost>
> 0: jdbc:phoenix:localhost> upsert into P_T02 (oid, code) values ('0001',
> 'v0001');
> 1 row affected (0.033 seconds)
> 0: jdbc:phoenix:localhost> upsert into P_T02 (oid, code) values ('0002',
> 'v0002');
> 1 row affected (0.004 seconds)
> 0: jdbc:phoenix:localhost>
> 0: jdbc:phoenix:localhost> select * from P_T02 where (oid, code) IN
> (('0001', 'v0001'), ('0002', 'v0002'));
> +--+--+
> | OID | CODE |
> +--+--+
> +--+--+
> {color:#FF}+*No rows selected (0.033 seconds)*+{color}
> 0: jdbc:phoenix:localhost> select * from P_T02 ;
> +--+--+
> | OID | CODE |
> +--+--+
> | 0002 | v0002 |
> | 0001 | v0001 |
> +--+--+
> 2 rows selected (0.016 seconds)
> 0: jdbc:phoenix:localhost>
> {noformat}
> *4.14.1 client -> 4.14.1 server*
> {noformat}
> Connected to: Phoenix (version 4.14)
> Driver: PhoenixEmbeddedDriver (version 4.14)
> Autocommit status: true
> Transaction isolation: TRANSACTION_READ_COMMITTED
> Building list of tables and columns for tab-completion (set fastconnect to
> true to skip)...
> 133/133 (100%) Done
> Done
> sqlline version 1.1.9
> 0: jdbc:phoenix:localhost>
> 0: jdbc:phoenix:localhost> CREATE table P_T01 (oid VARCHAR NOT NULL, code
> VARCHAR NOT NULL constraint pk primary key (oid DESC, code DESC));
> No rows affected (1.273 seconds)
> 0: jdbc:phoenix:localhost>
> 0: jdbc:phoenix:localhost> upsert into P_T01 (oid, code) values ('0001',
> 'v0001');
> 1 row affected (0.056 seconds)
> 0: jdbc:phoenix:localhost> upsert into P_T01 (oid, code) values ('0002',
> 'v0002');
> 1 row affected (0.004 seconds)
> 0: jdbc:phoenix:localhost>
> 0: jdbc:phoenix:localhost> select * from P_T01 where (oid, code) IN
> (('0001', 'v0001'), ('0002', 'v0002'));
> +--+--+
> | OID | CODE |
> +--+--+
> | 0002 | v0002 |
> | 0001 | v0001 |
> +--+--+
> 2 rows selected (0.051 seconds)
> 0: jdbc:phoenix:localhost> select * from P_T01 ;
> +--+--+
> | OID | CODE |
> +--+--+
> | 0002 | v0002 |
> | 0001 | v0001 |
> +--+--+
> 2 rows selected (0.017 seconds)
> 0: jdbc:phoenix:localhost>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Closed] (PHOENIX-5209) Cannot add non-PK column to table when the last PK column is of type VARBINARY or ARRAY
[
https://issues.apache.org/jira/browse/PHOENIX-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swaroopa Kadam closed PHOENIX-5209.
---
bulk closing of jiras after 4.14.3 release
> Cannot add non-PK column to table when the last PK column is of type
> VARBINARY or ARRAY
> ---
>
> Key: PHOENIX-5209
> URL: https://issues.apache.org/jira/browse/PHOENIX-5209
> Project: Phoenix
> Issue Type: Bug
>Reporter: Toshihiro Suzuki
>Assignee: Toshihiro Suzuki
>Priority: Major
> Fix For: 4.15.0, 5.1.0, 4.14.3
>
> Attachments: PHOENIX-5209.4.14-HBase-1.3.v1.patch,
> PHOENIX-5209.4.14-HBase-1.4.v1.patch, PHOENIX-5209.4.x-HBase-1.3.v1.patch,
> PHOENIX-5209.4.x-HBase-1.3.v2.patch, PHOENIX-5209.4.x-HBase-1.4.v1.patch,
> PHOENIX-5209.4.x-HBase-1.4.v2.patch, PHOENIX-5209.4.x-HBase-1.5.v1.patch,
> PHOENIX-5209.4.x-HBase-1.5.v2.patch, PHOENIX-5209.master.v1.patch,
> PHOENIX-5209.master.v2.patch
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Let's see we have the following table:
> {code}
> CREATE TABLE tbl (id VARBINARY PRIMARY KEY, col1 INTEGER)
> {code}
> The type of the primary key of this table is VARBINARY.
> And when we alter this table to add a new column:
> {code}
> ALTER TABLE tbl ADD col2 INTEGER
> {code}
> we are facing the following error:
> {code}
> java.sql.SQLException: ERROR 1015 (42J04): Cannot add column to table when
> the last PK column is of type VARBINARY or ARRAY. columnName=ID
> {code}
> I think we should be able to do it without the above error because we don't
> try to add a PK column.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Closed] (PHOENIX-4918) Apache Phoenix website Grammar page is running on an old version
[ https://issues.apache.org/jira/browse/PHOENIX-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam closed PHOENIX-4918. --- bulk closing of jiras after 4.14.3 release > Apache Phoenix website Grammar page is running on an old version > > > Key: PHOENIX-4918 > URL: https://issues.apache.org/jira/browse/PHOENIX-4918 > Project: Phoenix > Issue Type: Bug >Reporter: Xu Cang >Assignee: Xinyi Yan >Priority: Trivial > Fix For: 4.15.0, 5.1.0, 4.14.3 > > Attachments: PHOENIX-4918-4.14-branch.patch, > PHOENIX-4918-csv-format-fix.patch, PHOENIX-4918-svn-v2.patch, > PHOENIX-4918-svn.patch, PHOENIX-4918-v3.patch, PHOENIX-4918.patch > > Time Spent: 1h > Remaining Estimate: 0h > > For example this query example is incorrect: CREATE TABLE my_schema.my_table > ( id BIGINT not null primary key, date) > > [https://phoenix.apache.org/language/index.html] > I checked the master branch and 4.x branch, the code is correct though. > Meaning the website is using a very old version of phoenix.csv. > Any plan to update it? thanks. > FYI [~karanmehta93] > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (PHOENIX-5455) IndexedKeyValue creation fails after HBASE-22034
[ https://issues.apache.org/jira/browse/PHOENIX-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam updated PHOENIX-5455: Fix Version/s: 4.15.0 > IndexedKeyValue creation fails after HBASE-22034 > > > Key: PHOENIX-5455 > URL: https://issues.apache.org/jira/browse/PHOENIX-5455 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.15.0, 4.14.3 >Reporter: Geoffrey Jacoby >Priority: Blocker > Fix For: 4.15.0 > > > HBASE-22034 backported to branch-1 HBASE-21401 (adding several validation > checks to KeyValue creation) and HBASE-22032 (adding a null check for the row > key to KeyValue creation). It will first be released in HBase 1.5. > In Phoenix 4.14.2 we included PHOENIX-5188, which adds logic to initialize > IndexedKeyValues with the appropriate row key and offsets, so that it can > pass the new check in HBASE-22032. However, it did not correctly handle all > the checks in HBASE-21401. > When testing 4.14.3 of Phoenix with an HBase version containing HBASE-22034, > we see lots of errors like the following: > java.lang.IllegalArgumentException: Overflow when reading key length at > position=0, KeyValueBytesHex=foo, offset=0, length=3 > This will affect the future 4.15-HBase-1.5, and as well as any future release > of a 4.14.3 based on HBase-1.5 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (PHOENIX-5455) IndexedKeyValue creation fails after HBASE-22034
[ https://issues.apache.org/jira/browse/PHOENIX-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam updated PHOENIX-5455: Affects Version/s: 4.14.3 > IndexedKeyValue creation fails after HBASE-22034 > > > Key: PHOENIX-5455 > URL: https://issues.apache.org/jira/browse/PHOENIX-5455 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.14.3 >Reporter: Geoffrey Jacoby >Priority: Blocker > > HBASE-22034 backported to branch-1 HBASE-21401 (adding several validation > checks to KeyValue creation) and HBASE-22032 (adding a null check for the row > key to KeyValue creation). It will first be released in HBase 1.5. > In Phoenix 4.14.2 we included PHOENIX-5188, which adds logic to initialize > IndexedKeyValues with the appropriate row key and offsets, so that it can > pass the new check in HBASE-22032. However, it did not correctly handle all > the checks in HBASE-21401. > When testing 4.14.3 of Phoenix with an HBase version containing HBASE-22034, > we see lots of errors like the following: > java.lang.IllegalArgumentException: Overflow when reading key length at > position=0, KeyValueBytesHex=foo, offset=0, length=3 > This will affect the future 4.15-HBase-1.5, and as well as any future release > of a 4.14.3 based on HBase-1.5 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (PHOENIX-5455) IndexedKeyValue creation fails after HBASE-22034
[ https://issues.apache.org/jira/browse/PHOENIX-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam updated PHOENIX-5455: Affects Version/s: 4.15.0 > IndexedKeyValue creation fails after HBASE-22034 > > > Key: PHOENIX-5455 > URL: https://issues.apache.org/jira/browse/PHOENIX-5455 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.15.0, 4.14.3 >Reporter: Geoffrey Jacoby >Priority: Blocker > > HBASE-22034 backported to branch-1 HBASE-21401 (adding several validation > checks to KeyValue creation) and HBASE-22032 (adding a null check for the row > key to KeyValue creation). It will first be released in HBase 1.5. > In Phoenix 4.14.2 we included PHOENIX-5188, which adds logic to initialize > IndexedKeyValues with the appropriate row key and offsets, so that it can > pass the new check in HBASE-22032. However, it did not correctly handle all > the checks in HBASE-21401. > When testing 4.14.3 of Phoenix with an HBase version containing HBASE-22034, > we see lots of errors like the following: > java.lang.IllegalArgumentException: Overflow when reading key length at > position=0, KeyValueBytesHex=foo, offset=0, length=3 > This will affect the future 4.15-HBase-1.5, and as well as any future release > of a 4.14.3 based on HBase-1.5 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (PHOENIX-5419) Cleanup anonymous class in TracingQueryPlan
[ https://issues.apache.org/jira/browse/PHOENIX-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Jain updated PHOENIX-5419: Attachment: PHOENIX-5419-4.x-HBase-1.3.patch > Cleanup anonymous class in TracingQueryPlan > --- > > Key: PHOENIX-5419 > URL: https://issues.apache.org/jira/browse/PHOENIX-5419 > Project: Phoenix > Issue Type: Sub-task >Reporter: Ankit Jain >Assignee: Ankit Jain >Priority: Minor > Attachments: PHOENIX-5419-4.x-HBase-1.3.patch, PHOENIX-5419.patch, > PHOENIX-5419.v2.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Cleanup anonymous class in TracingQueryPlan -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (PHOENIX-5419) Cleanup anonymous class in TracingQueryPlan
[ https://issues.apache.org/jira/browse/PHOENIX-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Jain updated PHOENIX-5419: Attachment: PHOENIX-5419-4.x-HBase-1.3.patch > Cleanup anonymous class in TracingQueryPlan > --- > > Key: PHOENIX-5419 > URL: https://issues.apache.org/jira/browse/PHOENIX-5419 > Project: Phoenix > Issue Type: Sub-task >Reporter: Ankit Jain >Assignee: Ankit Jain >Priority: Minor > Attachments: PHOENIX-5419.patch, PHOENIX-5419.v2.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Cleanup anonymous class in TracingQueryPlan -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (PHOENIX-5419) Cleanup anonymous class in TracingQueryPlan
[ https://issues.apache.org/jira/browse/PHOENIX-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Jain updated PHOENIX-5419: Attachment: (was: PHOENIX-5419-4.x-HBase-1.3.patch) > Cleanup anonymous class in TracingQueryPlan > --- > > Key: PHOENIX-5419 > URL: https://issues.apache.org/jira/browse/PHOENIX-5419 > Project: Phoenix > Issue Type: Sub-task >Reporter: Ankit Jain >Assignee: Ankit Jain >Priority: Minor > Attachments: PHOENIX-5419.patch, PHOENIX-5419.v2.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Cleanup anonymous class in TracingQueryPlan -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (PHOENIX-5296) Ensure store file reader refcount is zero at end of relevant unit tests
[ https://issues.apache.org/jira/browse/PHOENIX-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Pal reassigned PHOENIX-5296: Assignee: Sandeep Pal > Ensure store file reader refcount is zero at end of relevant unit tests > --- > > Key: PHOENIX-5296 > URL: https://issues.apache.org/jira/browse/PHOENIX-5296 > Project: Phoenix > Issue Type: Test >Reporter: Andrew Purtell >Assignee: Sandeep Pal >Priority: Major > Labels: phoenix-hardening > Fix For: 4.15.1, 5.1.1 > > > Unit and integration tests for functional areas where the implementation > wraps scanners and uses a delegate pattern should check at the end of the > test that no scanners were leaked (check that all scanners including the > inner scanners were properly closed) by testing that the store reader > reference count is zero on all stores. > HBASE-22459 will offer a new metric and API which exposes this information. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (PHOENIX-5455) IndexedKeyValue creation fails after HBASE-22034
Geoffrey Jacoby created PHOENIX-5455: Summary: IndexedKeyValue creation fails after HBASE-22034 Key: PHOENIX-5455 URL: https://issues.apache.org/jira/browse/PHOENIX-5455 Project: Phoenix Issue Type: Bug Reporter: Geoffrey Jacoby HBASE-22034 backported to branch-1 HBASE-21401 (adding several validation checks to KeyValue creation) and HBASE-22032 (adding a null check for the row key to KeyValue creation). It will first be released in HBase 1.5. In Phoenix 4.14.2 we included PHOENIX-5188, which adds logic to initialize IndexedKeyValues with the appropriate row key and offsets, so that it can pass the new check in HBASE-22032. However, it did not correctly handle all the checks in HBASE-21401. When testing 4.14.3 of Phoenix with an HBase version containing HBASE-22034, we see lots of errors like the following: java.lang.IllegalArgumentException: Overflow when reading key length at position=0, KeyValueBytesHex=foo, offset=0, length=3 This will affect the future 4.15-HBase-1.5, and as well as any future release of a 4.14.3 based on HBase-1.5 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (PHOENIX-5260) Create new documentation page for UpdateStatisticsTool usage and options
[ https://issues.apache.org/jira/browse/PHOENIX-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan reassigned PHOENIX-5260: -- Assignee: Xinyi Yan > Create new documentation page for UpdateStatisticsTool usage and options > > > Key: PHOENIX-5260 > URL: https://issues.apache.org/jira/browse/PHOENIX-5260 > Project: Phoenix > Issue Type: Improvement >Reporter: Karan Mehta >Assignee: Xinyi Yan >Priority: Major > Labels: phoenix-hardening > > FYI [~yanxinyi] > It will be good to add this for new users before the release. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (PHOENIX-5454) Phoenix scripts start foreground java processes as child processes
[ https://issues.apache.org/jira/browse/PHOENIX-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] István Tóth reassigned PHOENIX-5454: Assignee: István Tóth > Phoenix scripts start foreground java processes as child processes > -- > > Key: PHOENIX-5454 > URL: https://issues.apache.org/jira/browse/PHOENIX-5454 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.1.0 >Reporter: István Tóth >Assignee: István Tóth >Priority: Minor > > Currently the phoenix scripts in python start the java process via > subprocess.call() or subprocess.popen() even when the java process has to run > in the foreground, and there is no cleanup required. > I propose that in these cases, we start java via os.exec*(). This has the > following advantages: > * There is no python process idling waiting for the java process to end, > reducing process count and memory consumption > * Signal handling is simplified (signals sent to the starting script are > received by the java process started) > * Return code handling is simplified (no need to check for and return error > codes from java in the startup script) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (PHOENIX-5454) Phoenix scripts start foreground java processes as child processes
István Tóth created PHOENIX-5454: Summary: Phoenix scripts start foreground java processes as child processes Key: PHOENIX-5454 URL: https://issues.apache.org/jira/browse/PHOENIX-5454 Project: Phoenix Issue Type: Improvement Affects Versions: 5.1.0 Reporter: István Tóth Currently the phoenix scripts in python start the java process via subprocess.call() or subprocess.popen() even when the java process has to run in the foreground, and there is no cleanup required. I propose that in these cases, we start java via os.exec*(). This has the following advantages: * There is no python process idling waiting for the java process to end, reducing process count and memory consumption * Signal handling is simplified (signals sent to the starting script are received by the java process started) * Return code handling is simplified (no need to check for and return error codes from java in the startup script) -- This message was sent by Atlassian Jira (v8.3.2#803003)
