You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2014/03/05 07:01:48 UTC
[jira] [Commented] (PHOENIX-110) Indexes with tenant-specific views
appear to be broken
[ https://issues.apache.org/jira/browse/PHOENIX-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13920556#comment-13920556 ]
ASF GitHub Bot commented on PHOENIX-110:
----------------------------------------
GitHub user elilevine opened a pull request:
https://github.com/apache/incubator-phoenix/pull/13
PHOENIX-110 Indexes with tenant-specific views appear to be broken
https://issues.apache.org/jira/browse/PHOENIX-110
Code to repro bug
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/elilevine/incubator-phoenix tenant-index-bug
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-phoenix/pull/13.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #13
----
commit 156333bf163b86892ca9a311656aeaf21e5814ee
Author: Eli Levine <el...@apache.org>
Date: 2014-03-03T23:54:43Z
Test views with case-sensitive table names
commit 531843a18948a01923363611b859fc0ef1c95bed
Author: Eli Levine <el...@apache.org>
Date: 2014-03-03T23:55:50Z
Test metadata scan when two diff tenants have tenant-specific tables with same name
commit 8836304d5333cd5999d13e6d3713e38903e8dcf1
Author: Eli Levine <el...@apache.org>
Date: 2014-03-05T00:02:13Z
Test multi-tenant views with salt and indexes using multiple views with same name
commit 7f99fe783783881f79a93e34c0d4d41a51109523
Author: Eli Levine <el...@apache.org>
Date: 2014-03-05T00:40:40Z
Merge latest from apache/incubator-phoenix
commit c0dfc070a1e5c6f168200719eb3bace51323b93b
Author: Eli Levine <el...@salesforce.com>
Date: 2014-03-05T05:43:28Z
Simple test to trigger possible bug in secondary indexes over tenant-specific views
commit 7b0aa26daa2e0d906adcaa95cece453e3edc6583
Author: Eli Levine <el...@salesforce.com>
Date: 2014-03-05T05:58:56Z
Merge latest from apache/incubator-phoenix
----
> Indexes with tenant-specific views appear to be broken
> ------------------------------------------------------
>
> Key: PHOENIX-110
> URL: https://issues.apache.org/jira/browse/PHOENIX-110
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Eli Levine
> Fix For: 3.0.0
>
>
> Getting the following stacktrace when inserting into a tenant-specific view that has a secondary index on it. Will send a pull req with code to repro.
> java.lang.IllegalArgumentException: Could not find expected ':' separator in index column name of "_INDEX_ID"
> at org.apache.phoenix.util.IndexUtil.getDataColumn(IndexUtil.java:117)
> at org.apache.phoenix.index.IndexMaintainer.create(IndexMaintainer.java:96)
> at org.apache.phoenix.schema.PTableImpl.getIndexMaintainer(PTableImpl.java:879)
> at org.apache.phoenix.index.IndexMaintainer.serialize(IndexMaintainer.java:146)
> at org.apache.phoenix.schema.PTableImpl.getIndexMaintainers(PTableImpl.java:891)
> at org.apache.phoenix.execute.MutationState.commit(MutationState.java:346)
> at org.apache.phoenix.jdbc.PhoenixConnection.commit(PhoenixConnection.java:355)
> at org.apache.phoenix.end2end.BaseTenantSpecificViewIndexTest.createAndVerifyIndex(BaseTenantSpecificViewIndexTest.java:104)
> at org.apache.phoenix.end2end.BaseTenantSpecificViewIndexTest.testUpdatableViewsWithSameNameDifferentTenants(BaseTenantSpecificViewIndexTest.java:68)
> at org.apache.phoenix.end2end.TenantSpecificViewIndexTest.testUpdatableViewsWithSameNameDifferentTenants(TenantSpecificViewIndexTest.java:30)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> 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.runLeaf(ParentRunner.java:271)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> 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:309)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
--
This message was sent by Atlassian JIRA
(v6.2#6252)