phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-110) Indexes with tenant-specific views appear to be broken
Date Wed, 05 Mar 2014 06:01:48 GMT


ASF GitHub Bot commented on PHOENIX-110:

GitHub user elilevine opened a pull request:

     PHOENIX-110  Indexes with tenant-specific views appear to be broken
    Code to repro bug

You can merge this pull request into a Git repository by running:

    $ git pull tenant-index-bug

Alternatively you can review and apply these changes as the patch at:

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 <>
Date:   2014-03-03T23:54:43Z

    Test views with case-sensitive table names

commit 531843a18948a01923363611b859fc0ef1c95bed
Author: Eli Levine <>
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 <>
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 <>
Date:   2014-03-05T00:40:40Z

    Merge latest from apache/incubator-phoenix

commit c0dfc070a1e5c6f168200719eb3bace51323b93b
Author: Eli Levine <>
Date:   2014-03-05T05:43:28Z

    Simple test to trigger possible bug in secondary indexes over tenant-specific views

commit 7b0aa26daa2e0d906adcaa95cece453e3edc6583
Author: Eli Levine <>
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:
>             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(
> 	at org.apache.phoenix.index.IndexMaintainer.create(
> 	at org.apache.phoenix.schema.PTableImpl.getIndexMaintainer(
> 	at org.apache.phoenix.index.IndexMaintainer.serialize(
> 	at org.apache.phoenix.schema.PTableImpl.getIndexMaintainers(
> 	at org.apache.phoenix.execute.MutationState.commit(
> 	at org.apache.phoenix.jdbc.PhoenixConnection.commit(
> 	at org.apache.phoenix.end2end.BaseTenantSpecificViewIndexTest.createAndVerifyIndex(
> 	at org.apache.phoenix.end2end.BaseTenantSpecificViewIndexTest.testUpdatableViewsWithSameNameDifferentTenants(
> 	at org.apache.phoenix.end2end.TenantSpecificViewIndexTest.testUpdatableViewsWithSameNameDifferentTenants(
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> 	at java.lang.reflect.Method.invoke(
> 	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(
> 	at
> 	at org.junit.runners.model.FrameworkMethod.invokeExplosively(
> 	at org.junit.internal.runners.statements.InvokeMethod.evaluate(
> 	at org.junit.internal.runners.statements.RunBefores.evaluate(
> 	at org.junit.internal.runners.statements.RunAfters.evaluate(
> 	at org.junit.runners.ParentRunner.runLeaf(
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(
> 	at org.junit.runners.ParentRunner$
> 	at org.junit.runners.ParentRunner$1.schedule(
> 	at org.junit.runners.ParentRunner.runChildren(
> 	at org.junit.runners.ParentRunner.access$000(
> 	at org.junit.runners.ParentRunner$2.evaluate(
> 	at org.junit.internal.runners.statements.RunBefores.evaluate(
> 	at org.junit.internal.runners.statements.RunAfters.evaluate(
> 	at
> 	at
> 	at
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(
> 	at
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(

This message was sent by Atlassian JIRA

View raw message