[jira] [Updated] (PHOENIX-4522) Fail to remove the schema from client-side cache
[
https://issues.apache.org/jira/browse/PHOENIX-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated PHOENIX-4522:
Description:
We always pass the wrong key to remove the schema
{code:title=PMetaDataImpl.java}
@Override
public void removeSchema(PSchema schema, long schemaTimeStamp) {
this.metaData.schemas.remove(SchemaUtil.getSchemaKey(schema.getSchemaName()));
}
{code}
was:
We always pass the wrong key to remove the schema
{code:PMetaDataImpl.java}
@Override
public void removeSchema(PSchema schema, long schemaTimeStamp) {
this.metaData.schemas.remove(SchemaUtil.getSchemaKey(schema.getSchemaName()));
}
{code}
> Fail to remove the schema from client-side cache
>
>
> Key: PHOENIX-4522
> URL: https://issues.apache.org/jira/browse/PHOENIX-4522
> Project: Phoenix
> Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Critical
> Fix For: 5.0.0, 4.14.0, 4.13.2, 4.13.2-cdh5.11.2
>
> Attachments: PHOENIX-4522.v0.patch
>
>
> We always pass the wrong key to remove the schema
> {code:title=PMetaDataImpl.java}
> @Override
> public void removeSchema(PSchema schema, long schemaTimeStamp) {
>
> this.metaData.schemas.remove(SchemaUtil.getSchemaKey(schema.getSchemaName()));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (PHOENIX-4459) Region assignments are failing for the test cases with extended clocks to support SCN
[
https://issues.apache.org/jira/browse/PHOENIX-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Soldatov updated PHOENIX-4459:
-
Attachment: PHOENIX-4459-v1.patch
[~an...@apache.org], [~rajeshbabu] could you take a look. Made the clock
autoadvance and disable the advance at particular moments (like when need to
do some actions at the same time). The only problem is the tenant views test.
Haven't found a way how to properly check the timestamp from the info, so at
the moment just removed those checks. If you have any suggestions feel free to
modify/add something.
> Region assignments are failing for the test cases with extended clocks to
> support SCN
> -
>
> Key: PHOENIX-4459
> URL: https://issues.apache.org/jira/browse/PHOENIX-4459
> Project: Phoenix
> Issue Type: Sub-task
>Reporter: Rajeshbabu Chintaguntla
>Assignee: Rajeshbabu Chintaguntla
> Labels: HBase-2.0
> Fix For: 5.0.0
>
> Attachments: PHOENIX-4459-v1.patch, jstack_PHOENIX-4459
>
>
> There are test cases using own clock are failing with TableNotFoundException
> during region assignment. The reason is the meta scan is not giving any
> results because of the past timestamps. Need to check in more details.
> Because of the region assignment failures during create table procedure hbase
> client wait for 30 mins. So not able to continue running the other tests as
> well.
> {noformat}
> 2017-12-14 16:48:03,153 ERROR [ProcExecWrkr-9]
> org.apache.hadoop.hbase.master.TableStateManager(135): Unable to get table
> T08 state
> org.apache.hadoop.hbase.TableNotFoundException: T08
> at
> org.apache.hadoop.hbase.master.TableStateManager.getTableState(TableStateManager.java:175)
> at
> org.apache.hadoop.hbase.master.TableStateManager.isTableState(TableStateManager.java:132)
> at
> org.apache.hadoop.hbase.master.assignment.AssignProcedure.startTransition(AssignProcedure.java:161)
> at
> org.apache.hadoop.hbase.master.assignment.RegionTransitionProcedure.execute(RegionTransitionProcedure.java:294)
> at
> org.apache.hadoop.hbase.master.assignment.RegionTransitionProcedure.execute(RegionTransitionProcedure.java:85)
> at
> org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1452)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1221)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$800(ProcedureExecutor.java:77)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:1731)
> {noformat}
> List of tests hanging because of this:-
> ExplainPlanWithStatsEnabledIT#testBytesRowsForSelectOnTenantViews
> ConcurrentMutationsIT
> PartialIndexRebuilderIT
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (PHOENIX-1661) Implement built-in functions for JSON
[
https://issues.apache.org/jira/browse/PHOENIX-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319809#comment-16319809
]
Wen-Hsiu Chang commented on PHOENIX-1661:
-
Hi, [~jamestaylor]
We want to try this issue, and we put the patch below. Please take a look.
In brief, we take a look at the JSON built-in functions that are implemented in
Hive(https://cwiki.apache.org/confluence/display/Hive/LanguageManual+UDF#LanguageManualUDF-get_json_object),
and we implement the same get_json_object built-in function in phoenix.
And in this method, the json object should store in one hbase cell.
{code:java}
String get_json_object (String json, String path)
{code}
For example,
{code:java}
SELECT get_json_object(json_col,"$.name") FROM my_table;
{code}
[^PHOENIX-1661-00.patch]
The pdf [^Implement built-in functions for JSON.pdf] says,
we want to do three built in function
1. get_json_object
2. set_json_object
3. remove_json_object
> Implement built-in functions for JSON
> -
>
> Key: PHOENIX-1661
> URL: https://issues.apache.org/jira/browse/PHOENIX-1661
> Project: Phoenix
> Issue Type: Sub-task
>Reporter: James Taylor
>Assignee: LeiWang
> Labels: JSON, Java, SQL, gsoc2015, mentor
> Attachments: Implement built-in functions for JSON.pdf,
> PHOENIX-1661-00.patch, PHOENIX-1661.patch,
> PhoenixJSONSpecification-First-Draft.pdf
>
>
> Take a look at the JSON built-in functions that are implemented in Postgres
> (http://www.postgresql.org/docs/9.3/static/functions-json.html) and implement
> the same for Phoenix in Java following this guide:
> http://phoenix-hbase.blogspot.com/2013/04/how-to-add-your-own-built-in-function.html
> Examples of functions include ARRAY_TO_JSON, ROW_TO_JSON, TO_JSON, etc. The
> implementation of these built-in functions will be impacted by how JSON is
> stored in Phoenix. See PHOENIX-628. An initial implementation could work off
> of a simple text-based JSON representation and then when a native JSON type
> is implemented, they could be reworked to be more efficient.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (PHOENIX-1661) Implement built-in functions for JSON
[
https://issues.apache.org/jira/browse/PHOENIX-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319809#comment-16319809
]
Wen-Hsiu Chang edited comment on PHOENIX-1661 at 1/10/18 7:27 AM:
--
Hi, [~jamestaylor]
We want to try this issue, and we put the patch below. Please take a look.
In brief, we take a look at the JSON built-in functions that are implemented in
Hive(https://cwiki.apache.org/confluence/display/Hive/LanguageManual+UDF#LanguageManualUDF-get_json_object),
and we implement the same get_json_object built-in function in phoenix.
And in this method, the json object should store in one hbase cell.
{code:java}
String get_json_object (String json, String path)
{code}
For example,
{code:java}
SELECT get_json_object(json_col,"$.name") FROM my_table;
{code}
The pdf [^Implement built-in functions for JSON.pdf] says,
we want to do three built-in functions.
1. get_json_object
2. set_json_object
3. remove_json_object
[^PHOENIX-1661-00.patch]
was (Author: ashiou):
Hi, [~jamestaylor]
We want to try this issue, and we put the patch below. Please take a look.
In brief, we take a look at the JSON built-in functions that are implemented in
Hive(https://cwiki.apache.org/confluence/display/Hive/LanguageManual+UDF#LanguageManualUDF-get_json_object),
and we implement the same get_json_object built-in function in phoenix.
And in this method, the json object should store in one hbase cell.
{code:java}
String get_json_object (String json, String path)
{code}
For example,
{code:java}
SELECT get_json_object(json_col,"$.name") FROM my_table;
{code}
[^PHOENIX-1661-00.patch]
The pdf [^Implement built-in functions for JSON.pdf] says,
we want to do three built in function
1. get_json_object
2. set_json_object
3. remove_json_object
> Implement built-in functions for JSON
> -
>
> Key: PHOENIX-1661
> URL: https://issues.apache.org/jira/browse/PHOENIX-1661
> Project: Phoenix
> Issue Type: Sub-task
>Reporter: James Taylor
>Assignee: LeiWang
> Labels: JSON, Java, SQL, gsoc2015, mentor
> Attachments: Implement built-in functions for JSON.pdf,
> PHOENIX-1661-00.patch, PHOENIX-1661.patch,
> PhoenixJSONSpecification-First-Draft.pdf
>
>
> Take a look at the JSON built-in functions that are implemented in Postgres
> (http://www.postgresql.org/docs/9.3/static/functions-json.html) and implement
> the same for Phoenix in Java following this guide:
> http://phoenix-hbase.blogspot.com/2013/04/how-to-add-your-own-built-in-function.html
> Examples of functions include ARRAY_TO_JSON, ROW_TO_JSON, TO_JSON, etc. The
> implementation of these built-in functions will be impacted by how JSON is
> stored in Phoenix. See PHOENIX-628. An initial implementation could work off
> of a simple text-based JSON representation and then when a native JSON type
> is implemented, they could be reworked to be more efficient.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (PHOENIX-4514) A incorrect key object is used in SequenceManager#validateSequences
[
https://issues.apache.org/jira/browse/PHOENIX-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated PHOENIX-4514:
Attachment: PHOENIX.4514.v0.patch
> A incorrect key object is used in SequenceManager#validateSequences
> ---
>
> Key: PHOENIX-4514
> URL: https://issues.apache.org/jira/browse/PHOENIX-4514
> Project: Phoenix
> Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Minor
> Attachments: PHOENIX.4514.v0.patch
>
>
> nextSequences.get( i ) -> nextSequences.get( i ).getSequenceKey()
> {code:title=SequenceManager.java}
> for (int i = 0; i < nextSequences.size(); i++) {
> sequencePosition[i] =
> sequenceMap.get(nextSequences.get(i)).getIndex();
> }
> {code}
> It won't cause bug since the impl of SequenceAllocation#hashCode is equal
> with SequenceKey#hashCode. However, it still a potential bug so a fix is
> necessary I believe.
> {code:title=SequenceAllocation.java}
> @Override
> public int hashCode() {
> return sequenceKey.hashCode();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (PHOENIX-4471) Time related queries are failing
[ https://issues.apache.org/jira/browse/PHOENIX-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319825#comment-16319825 ] Ankit Singhal commented on PHOENIX-4471: bq. there’s a new coprocessor we added that creates a new ScanInfo with KEEP_DELETED_CELLS=true when a point-in-time query is performed. Can we look at how to do the same in 2.0? This is important functionality that our IndexScrutiny tool relies on, so we need to figure out a way to keep it. Yes [~giacomotaylor], I already have PHOENIX-4378 open for the same. > Time related queries are failing > - > > Key: PHOENIX-4471 > URL: https://issues.apache.org/jira/browse/PHOENIX-4471 > Project: Phoenix > Issue Type: Sub-task >Reporter: Ankit Singhal >Assignee: Ankit Singhal > Labels: HBase-2.0 > Fix For: 5.0.0 > > > [ERROR] Tests run: 42, Failures: 26, Errors: 0, Skipped: 0, Time elapsed: > 259.606 s <<< FAILURE! - in org.apache.phoenix.end2end.PointInTimeQueryIT -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PHOENIX-4459) Region assignments are failing for the test cases with extended clocks to support SCN
[
https://issues.apache.org/jira/browse/PHOENIX-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankit Singhal updated PHOENIX-4459:
---
Description:
There are test cases using own clock are failing with TableNotFoundException
during region assignment. The reason is the meta scan is not giving any results
because of the past timestamps. Need to check in more details. Because of the
region assignment failures during create table procedure hbase client wait for
30 mins. So not able to continue running the other tests as well.
{noformat}
2017-12-14 16:48:03,153 ERROR [ProcExecWrkr-9]
org.apache.hadoop.hbase.master.TableStateManager(135): Unable to get table
T08 state
org.apache.hadoop.hbase.TableNotFoundException: T08
at
org.apache.hadoop.hbase.master.TableStateManager.getTableState(TableStateManager.java:175)
at
org.apache.hadoop.hbase.master.TableStateManager.isTableState(TableStateManager.java:132)
at
org.apache.hadoop.hbase.master.assignment.AssignProcedure.startTransition(AssignProcedure.java:161)
at
org.apache.hadoop.hbase.master.assignment.RegionTransitionProcedure.execute(RegionTransitionProcedure.java:294)
at
org.apache.hadoop.hbase.master.assignment.RegionTransitionProcedure.execute(RegionTransitionProcedure.java:85)
at
org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1452)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1221)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$800(ProcedureExecutor.java:77)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:1731)
{noformat}
List of tests failing because of this:-
ExplainPlanWithStatsEnabledIT#testBytesRowsForSelectOnTenantViews
ConcurrentMutationsIT
PartialIndexRebuilderIT
was:
There are test cases using own clock are failing with TableNotFoundException
during region assignment. The reason is the meta scan is not giving any results
because of the past timestamps. Need to check in more details. Because of the
region assignment failures during create table procedure hbase client wait for
30 mins. So not able to continue running the other tests as well.
{noformat}
2017-12-14 16:48:03,153 ERROR [ProcExecWrkr-9]
org.apache.hadoop.hbase.master.TableStateManager(135): Unable to get table
T08 state
org.apache.hadoop.hbase.TableNotFoundException: T08
at
org.apache.hadoop.hbase.master.TableStateManager.getTableState(TableStateManager.java:175)
at
org.apache.hadoop.hbase.master.TableStateManager.isTableState(TableStateManager.java:132)
at
org.apache.hadoop.hbase.master.assignment.AssignProcedure.startTransition(AssignProcedure.java:161)
at
org.apache.hadoop.hbase.master.assignment.RegionTransitionProcedure.execute(RegionTransitionProcedure.java:294)
at
org.apache.hadoop.hbase.master.assignment.RegionTransitionProcedure.execute(RegionTransitionProcedure.java:85)
at
org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1452)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1221)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$800(ProcedureExecutor.java:77)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:1731)
{noformat}
> Region assignments are failing for the test cases with extended clocks to
> support SCN
> -
>
> Key: PHOENIX-4459
> URL: https://issues.apache.org/jira/browse/PHOENIX-4459
> Project: Phoenix
> Issue Type: Sub-task
>Reporter: Rajeshbabu Chintaguntla
>Assignee: Rajeshbabu Chintaguntla
> Labels: HBase-2.0
> Fix For: 5.0.0
>
> Attachments: jstack_PHOENIX-4459
>
>
> There are test cases using own clock are failing with TableNotFoundException
> during region assignment. The reason is the meta scan is not giving any
> results because of the past timestamps. Need to check in more details.
> Because of the region assignment failures during create table procedure hbase
> client wait for 30 mins. So not able to continue running the other tests as
> well.
> {noformat}
> 2017-12-14 16:48:03,153 ERROR [ProcExecWrkr-9]
> org.apache.hadoop.hbase.master.TableStateManager(135): Unable to get table
> T08 state
> org.apache.hadoop.hbase.TableNotFoundException: T08
> at
> org.apache.hadoop.hbase.master.TableStateManager.getTableState
[jira] [Updated] (PHOENIX-4459) Region assignments are failing for the test cases with extended clocks to support SCN
[
https://issues.apache.org/jira/browse/PHOENIX-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankit Singhal updated PHOENIX-4459:
---
Description:
There are test cases using own clock are failing with TableNotFoundException
during region assignment. The reason is the meta scan is not giving any results
because of the past timestamps. Need to check in more details. Because of the
region assignment failures during create table procedure hbase client wait for
30 mins. So not able to continue running the other tests as well.
{noformat}
2017-12-14 16:48:03,153 ERROR [ProcExecWrkr-9]
org.apache.hadoop.hbase.master.TableStateManager(135): Unable to get table
T08 state
org.apache.hadoop.hbase.TableNotFoundException: T08
at
org.apache.hadoop.hbase.master.TableStateManager.getTableState(TableStateManager.java:175)
at
org.apache.hadoop.hbase.master.TableStateManager.isTableState(TableStateManager.java:132)
at
org.apache.hadoop.hbase.master.assignment.AssignProcedure.startTransition(AssignProcedure.java:161)
at
org.apache.hadoop.hbase.master.assignment.RegionTransitionProcedure.execute(RegionTransitionProcedure.java:294)
at
org.apache.hadoop.hbase.master.assignment.RegionTransitionProcedure.execute(RegionTransitionProcedure.java:85)
at
org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1452)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1221)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$800(ProcedureExecutor.java:77)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:1731)
{noformat}
List of tests hanging because of this:-
ExplainPlanWithStatsEnabledIT#testBytesRowsForSelectOnTenantViews
ConcurrentMutationsIT
PartialIndexRebuilderIT
was:
There are test cases using own clock are failing with TableNotFoundException
during region assignment. The reason is the meta scan is not giving any results
because of the past timestamps. Need to check in more details. Because of the
region assignment failures during create table procedure hbase client wait for
30 mins. So not able to continue running the other tests as well.
{noformat}
2017-12-14 16:48:03,153 ERROR [ProcExecWrkr-9]
org.apache.hadoop.hbase.master.TableStateManager(135): Unable to get table
T08 state
org.apache.hadoop.hbase.TableNotFoundException: T08
at
org.apache.hadoop.hbase.master.TableStateManager.getTableState(TableStateManager.java:175)
at
org.apache.hadoop.hbase.master.TableStateManager.isTableState(TableStateManager.java:132)
at
org.apache.hadoop.hbase.master.assignment.AssignProcedure.startTransition(AssignProcedure.java:161)
at
org.apache.hadoop.hbase.master.assignment.RegionTransitionProcedure.execute(RegionTransitionProcedure.java:294)
at
org.apache.hadoop.hbase.master.assignment.RegionTransitionProcedure.execute(RegionTransitionProcedure.java:85)
at
org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1452)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1221)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$800(ProcedureExecutor.java:77)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:1731)
{noformat}
List of tests failing because of this:-
ExplainPlanWithStatsEnabledIT#testBytesRowsForSelectOnTenantViews
ConcurrentMutationsIT
PartialIndexRebuilderIT
> Region assignments are failing for the test cases with extended clocks to
> support SCN
> -
>
> Key: PHOENIX-4459
> URL: https://issues.apache.org/jira/browse/PHOENIX-4459
> Project: Phoenix
> Issue Type: Sub-task
>Reporter: Rajeshbabu Chintaguntla
>Assignee: Rajeshbabu Chintaguntla
> Labels: HBase-2.0
> Fix For: 5.0.0
>
> Attachments: jstack_PHOENIX-4459
>
>
> There are test cases using own clock are failing with TableNotFoundException
> during region assignment. The reason is the meta scan is not giving any
> results because of the past timestamps. Need to check in more details.
> Because of the region assignment failures during create table procedure hbase
> client wait for 30 mins. So not able to continue running the other tests as
> well.
> {noformat}
> 2017-12-14 16:48:03,153 ERROR [ProcExecWrkr-9]
> org.apache.hadoop.hbase.master.TableStateManager(135): Unable to get tab
[jira] [Updated] (PHOENIX-4523) phoenix.schema.isNamespaceMappingEnabled problem
[
https://issues.apache.org/jira/browse/PHOENIX-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flavio Pompermaier updated PHOENIX-4523:
Description:
I'm using Phoenix 4.13 for CDH 5.11.2 parcel and enabling schemas made my code
unusable.
I think that this is not a bug of the CDH release, but of all 4.13.x releases.
I have many parallel Phoenix connections and I always get the following
exception:
{code:java}
Caused by: java.sql.SQLException:
org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.hbase.TableExistsException):
SYSTEM:MUTEX
at
org.apache.phoenix.query.ConnectionQueryServicesImpl$12.call(ConnectionQueryServicesImpl.java:2492)
at
org.apache.phoenix.query.ConnectionQueryServicesImpl$12.call(ConnectionQueryServicesImpl.java:2384)
at
org.apache.phoenix.util.PhoenixContextExecutor.call(PhoenixContextExecutor.java:76)
at
org.apache.phoenix.query.ConnectionQueryServicesImpl.init(ConnectionQueryServicesImpl.java:2384)
at
org.apache.phoenix.jdbc.PhoenixDriver.getConnectionQueryServices(PhoenixDriver.java:255)
at
org.apache.phoenix.jdbc.PhoenixEmbeddedDriver.createConnection(PhoenixEmbeddedDriver.java:150)
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:270)
{code}
This is caused by the fact that all the times the SYSTEM tables are recreated,
and this cannot be done simultaneously.
Trying to debug the issue I found that in
ConnectionQueryServicesImpl.createSysMutexTable() the call to
getSystemTableNames() always return an empty array and the SYSTEM:MUTEX table
is always recreated.
This because getSystemTableNames() doesn't consider the case when system tables
have namespace enabled. Right now that method tries to get all tables starting
with *SYSTEM.\**, while it should try to get the list of *SYSTEM:\** tables..
I hope this could get fixed very soon,
Flavio
was:
I'm using Phoenix 4.13 for CDH 5.11.2 parcel and enabling schemas made my code
unusable.
I think that this is not a bug of the CDH release, but of all 4.13.x releases.
I have many parallel Phoenix connections and I always get the following
exception:
{code:java}
Caused by: java.sql.SQLException:
org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.hbase.TableExistsException):
SYSTEM:MUTEX
at
org.apache.phoenix.query.ConnectionQueryServicesImpl$12.call(ConnectionQueryServicesImpl.java:2492)
at
org.apache.phoenix.query.ConnectionQueryServicesImpl$12.call(ConnectionQueryServicesImpl.java:2384)
at
org.apache.phoenix.util.PhoenixContextExecutor.call(PhoenixContextExecutor.java:76)
at
org.apache.phoenix.query.ConnectionQueryServicesImpl.init(ConnectionQueryServicesImpl.java:2384)
at
org.apache.phoenix.jdbc.PhoenixDriver.getConnectionQueryServices(PhoenixDriver.java:255)
at
org.apache.phoenix.jdbc.PhoenixEmbeddedDriver.createConnection(PhoenixEmbeddedDriver.java:150)
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:270)
{code}
This is caused by the fact that all the times the SYSTEM tables are recreated,
and this cannot be done simultaneously.
Trying to debug the issue I found that in
ConnectionQueryServicesImpl.createSysMutexTable() the call to
getSystemTableNames() always return an empty array and the SYSTEM.MUTEX table
is always recreated.
This because getSystemTableNames() doesn't consider the case when system tables
have namespace enabled. Right now that method tries to get all tables starting
with *SYSTEM.\**, while it should try to get the list of *SYSTEM:\** tables..
I hope this could get fixed very soon,
Flavio
> phoenix.schema.isNamespaceMappingEnabled problem
>
>
> Key: PHOENIX-4523
> URL: https://issues.apache.org/jira/browse/PHOENIX-4523
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.13.1
>Reporter: Flavio Pompermaier
>
> I'm using Phoenix 4.13 for CDH 5.11.2 parcel and enabling schemas made my
> code unusable.
> I think that this is not a bug of the CDH release, but of all 4.13.x releases.
> I have many parallel Phoenix connections and I always get the following
> exception:
> {code:java}
> Caused by: java.sql.SQLException:
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.hbase.TableExistsException):
> SYSTEM:MUTEX
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl$12.call(ConnectionQueryServicesImpl.java:2492)
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl$12.call(ConnectionQueryServicesImpl.java:23
[jira] [Commented] (PHOENIX-4523) phoenix.schema.isNamespaceMappingEnabled problem
[
https://issues.apache.org/jira/browse/PHOENIX-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318823#comment-16318823
]
James Taylor commented on PHOENIX-4523:
---
[~karanmehta93] or [~tdsilva] - looks like a general issue with namespace
enablement. Any insights?
> phoenix.schema.isNamespaceMappingEnabled problem
>
>
> Key: PHOENIX-4523
> URL: https://issues.apache.org/jira/browse/PHOENIX-4523
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.13.1
>Reporter: Flavio Pompermaier
>
> I'm using Phoenix 4.13 for CDH 5.11.2 parcel and enabling schemas made my
> code unusable.
> I think that this is not a bug of the CDH release, but of all 4.13.x releases.
> I have many parallel Phoenix connections and I always get the following
> exception:
> {code:java}
> Caused by: java.sql.SQLException:
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.hbase.TableExistsException):
> SYSTEM:MUTEX
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl$12.call(ConnectionQueryServicesImpl.java:2492)
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl$12.call(ConnectionQueryServicesImpl.java:2384)
> at
> org.apache.phoenix.util.PhoenixContextExecutor.call(PhoenixContextExecutor.java:76)
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl.init(ConnectionQueryServicesImpl.java:2384)
> at
> org.apache.phoenix.jdbc.PhoenixDriver.getConnectionQueryServices(PhoenixDriver.java:255)
> at
> org.apache.phoenix.jdbc.PhoenixEmbeddedDriver.createConnection(PhoenixEmbeddedDriver.java:150)
> 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:270)
> {code}
> This is caused by the fact that all the times the SYSTEM tables are
> recreated, and this cannot be done simultaneously.
> Trying to debug the issue I found that in
> ConnectionQueryServicesImpl.createSysMutexTable() the call to
> getSystemTableNames() always return an empty array and the SYSTEM:MUTEX
> table is always recreated.
> This because getSystemTableNames() doesn't consider the case when system
> tables have namespace enabled. Right now that method tries to get all tables
> starting with *SYSTEM.\**, while it should try to get the list of *SYSTEM:\**
> tables..
> I hope this could get fixed very soon,
> Flavio
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (PHOENIX-3711) Convert static methods which create PTables in PTableImpl to a Builder pattern
[ https://issues.apache.org/jira/browse/PHOENIX-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] churro morales closed PHOENIX-3711. --- > Convert static methods which create PTables in PTableImpl to a Builder pattern > -- > > Key: PHOENIX-3711 > URL: https://issues.apache.org/jira/browse/PHOENIX-3711 > Project: Phoenix > Issue Type: Task >Reporter: churro morales >Assignee: churro morales > > It will be nice to use a builder pattern such that we do not have to > constantly create static methods for one-off creations of our PTables. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (PHOENIX-3711) Convert static methods which create PTables in PTableImpl to a Builder pattern
[ https://issues.apache.org/jira/browse/PHOENIX-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] churro morales reassigned PHOENIX-3711: --- Assignee: (was: churro morales) > Convert static methods which create PTables in PTableImpl to a Builder pattern > -- > > Key: PHOENIX-3711 > URL: https://issues.apache.org/jira/browse/PHOENIX-3711 > Project: Phoenix > Issue Type: Task >Reporter: churro morales > > It will be nice to use a builder pattern such that we do not have to > constantly create static methods for one-off creations of our PTables. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (PHOENIX-4270) IndexTool and IndexScrutiny Tool should optionally flush and delete snapshot after runs
[ https://issues.apache.org/jira/browse/PHOENIX-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] churro morales reassigned PHOENIX-4270: --- Assignee: (was: churro morales) > IndexTool and IndexScrutiny Tool should optionally flush and delete snapshot > after runs > --- > > Key: PHOENIX-4270 > URL: https://issues.apache.org/jira/browse/PHOENIX-4270 > Project: Phoenix > Issue Type: Bug >Reporter: churro morales > Attachments: PHOENIX-4270.patch > > > If the IndexTool or IndexScrutiny tool run with the snapshot option and the > timestamp is before the hbase.regionserver.optionalcacheflushinterval then > they should skip flushing as whatever is in the memstore will not be read by > the scanners and takes extra overhead. > Additionally both of these jobs should cleanup their snapshots after they > complete or this will take up dfs capacity unnecessarily. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (PHOENIX-4471) Time related queries are failing
[ https://issues.apache.org/jira/browse/PHOENIX-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318973#comment-16318973 ] James Taylor commented on PHOENIX-4471: --- [~an...@apache.org] - there’s a new coprocessor we added that creates a new ScanInfo with KEEP_DELETED_CELLS=true when a point-in-time query is performed. Can we look at how to do the same in 2.0? This is important functionality that our IndexScrutiny tool relies on, so we need to figure out a way to keep it. > Time related queries are failing > - > > Key: PHOENIX-4471 > URL: https://issues.apache.org/jira/browse/PHOENIX-4471 > Project: Phoenix > Issue Type: Sub-task >Reporter: Ankit Singhal >Assignee: Ankit Singhal > Labels: HBase-2.0 > Fix For: 5.0.0 > > > [ERROR] Tests run: 42, Failures: 26, Errors: 0, Skipped: 0, Time elapsed: > 259.606 s <<< FAILURE! - in org.apache.phoenix.end2end.PointInTimeQueryIT -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (PHOENIX-4372) Distribution of Apache Phoenix 4.13 for CDH 5.11.2
[ https://issues.apache.org/jira/browse/PHOENIX-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319091#comment-16319091 ] Pedro Boado commented on PHOENIX-4372: -- [~giacomotaylor] any update on the artifact generation? > Distribution of Apache Phoenix 4.13 for CDH 5.11.2 > -- > > Key: PHOENIX-4372 > URL: https://issues.apache.org/jira/browse/PHOENIX-4372 > Project: Phoenix > Issue Type: Task >Affects Versions: 4.13.0 >Reporter: Pedro Boado >Assignee: Pedro Boado >Priority: Minor > Labels: cdh > Attachments: PHOENIX-4372-v2.patch, PHOENIX-4372-v3.patch, > PHOENIX-4372-v4.patch, PHOENIX-4372-v5.patch, PHOENIX-4372-v6.patch, > PHOENIX-4372-v7.patch, PHOENIX-4372.patch > > > Changes required on top of branch 4.13-HBase-1.2 for creating a parcel of > Apache Phoenix 4.13.0 for CDH 5.11.2 . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PHOENIX-4414) Exception while using database metadata commands on tenant specific connection
[
https://issues.apache.org/jira/browse/PHOENIX-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mujtaba Chohan updated PHOENIX-4414:
Attachment: PHOENIX-4414_v2.patch
Added a unit test as well.
> Exception while using database metadata commands on tenant specific connection
> --
>
> Key: PHOENIX-4414
> URL: https://issues.apache.org/jira/browse/PHOENIX-4414
> Project: Phoenix
> Issue Type: Bug
>Reporter: Mujtaba Chohan
>Assignee: Mujtaba Chohan
>Priority: Minor
> Attachments: PHOENIX-4414.patch, PHOENIX-4414_v2.patch
>
>
> This is when using tenant specific connection from Sqlline.
> {noformat}
> Error: ERROR 602 (42P00): Syntax error. Missing "LPAREN" at line 2, column
> 746. (state=42P00,code=602)
> org.apache.phoenix.exception.PhoenixParserException: ERROR 602 (42P00):
> Syntax error. Missing "LPAREN" at line 2, column 746.
> at
> org.apache.phoenix.exception.PhoenixParserException.newException(PhoenixParserException.java:33)
> at org.apache.phoenix.parse.SQLParser.parseStatement(SQLParser.java:111)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$PhoenixStatementParser.parseStatement(PhoenixStatement.java:1529)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.parseStatement(PhoenixStatement.java:1612)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:1653)
> at
> org.apache.phoenix.jdbc.PhoenixDatabaseMetaData.getColumns(PhoenixDatabaseMetaData.java:557)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (PHOENIX-4372) Distribution of Apache Phoenix 4.13 for CDH 5.11.2
[ https://issues.apache.org/jira/browse/PHOENIX-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319203#comment-16319203 ] James Taylor commented on PHOENIX-4372: --- Was thinking PHOENIX-4523 may be a blocker, but if not, we can proceed now. Your call. > Distribution of Apache Phoenix 4.13 for CDH 5.11.2 > -- > > Key: PHOENIX-4372 > URL: https://issues.apache.org/jira/browse/PHOENIX-4372 > Project: Phoenix > Issue Type: Task >Affects Versions: 4.13.0 >Reporter: Pedro Boado >Assignee: Pedro Boado >Priority: Minor > Labels: cdh > Attachments: PHOENIX-4372-v2.patch, PHOENIX-4372-v3.patch, > PHOENIX-4372-v4.patch, PHOENIX-4372-v5.patch, PHOENIX-4372-v6.patch, > PHOENIX-4372-v7.patch, PHOENIX-4372.patch > > > Changes required on top of branch 4.13-HBase-1.2 for creating a parcel of > Apache Phoenix 4.13.0 for CDH 5.11.2 . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (PHOENIX-4372) Distribution of Apache Phoenix 4.13 for CDH 5.11.2
[ https://issues.apache.org/jira/browse/PHOENIX-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319242#comment-16319242 ] Pedro Boado commented on PHOENIX-4372: -- Agree it looks like a blocker. But I'm just worried we are loosing momentum. > Distribution of Apache Phoenix 4.13 for CDH 5.11.2 > -- > > Key: PHOENIX-4372 > URL: https://issues.apache.org/jira/browse/PHOENIX-4372 > Project: Phoenix > Issue Type: Task >Affects Versions: 4.13.0 >Reporter: Pedro Boado >Assignee: Pedro Boado >Priority: Minor > Labels: cdh > Attachments: PHOENIX-4372-v2.patch, PHOENIX-4372-v3.patch, > PHOENIX-4372-v4.patch, PHOENIX-4372-v5.patch, PHOENIX-4372-v6.patch, > PHOENIX-4372-v7.patch, PHOENIX-4372.patch > > > Changes required on top of branch 4.13-HBase-1.2 for creating a parcel of > Apache Phoenix 4.13.0 for CDH 5.11.2 . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (PHOENIX-4076) Move master branch up to HBase 1.4.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/PHOENIX-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319459#comment-16319459 ] Lars Hofhansl edited comment on PHOENIX-4076 at 1/10/18 12:33 AM: -- Now that there's an official release for HBase 1.4.0, let's do it. Edit: And let's drop -1.1, and -1.2? was (Author: lhofhansl): Now that there's an official release for HBase 1.4.0, let's do it. > Move master branch up to HBase 1.4.0-SNAPSHOT > - > > Key: PHOENIX-4076 > URL: https://issues.apache.org/jira/browse/PHOENIX-4076 > Project: Phoenix > Issue Type: Bug >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Attachments: PHOENIX-4076.patch > > > Move master branch up to HBase 1.4.0-SNAPSHOT. > There are some compilation problems. > Valid compatibility breaks are addressed and fixed by HBASE-18431. This > analysis is a compilation attempt of Phoenix master branch against > 1.4.0-SNAPSHOT artifacts including the HBASE-18431 changes. > HBASE-16584 removed PayloadCarryingRpcController, breaking compilation of > MetadataRpcController, InterRegionServerIndexRpcControllerFactory, > IndexRpcController, ClientRpcControllerFactory, and > InterRegionServerMetadataRpcControllerFactory. This class was annotated as > Private so was fair game to remove. It will be gone in HBase 1.4.x and up. > DelegateRegionObserver needs to implement added interface method > postCommitStoreFile. > DelegateHTable, TephraTransactionTable, and OmidTransactionTable need to > implement added interface methods for getting and setting read and write > timeouts. > PhoenixRpcScheduler needs to implement added interface methods for getting > handler counts. > Store file readers/writers/scanners have been refactored and the local index > implementation, which implements or overrides parts of this refactored > hierarchy will have to also be refactored. > DelegateRegionCoprocessorEnvironment needs to implement added method > getMetricRegistryForRegionServer > Another issue with IndexRpcController: incompatible types: int cannot be > converted to org.apache.hadoop.hbase.TableName -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (PHOENIX-4076) Move master branch up to HBase 1.4.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/PHOENIX-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319459#comment-16319459 ] Lars Hofhansl commented on PHOENIX-4076: Now that there's an official release for HBase 1.4.0, let's do it. > Move master branch up to HBase 1.4.0-SNAPSHOT > - > > Key: PHOENIX-4076 > URL: https://issues.apache.org/jira/browse/PHOENIX-4076 > Project: Phoenix > Issue Type: Bug >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Attachments: PHOENIX-4076.patch > > > Move master branch up to HBase 1.4.0-SNAPSHOT. > There are some compilation problems. > Valid compatibility breaks are addressed and fixed by HBASE-18431. This > analysis is a compilation attempt of Phoenix master branch against > 1.4.0-SNAPSHOT artifacts including the HBASE-18431 changes. > HBASE-16584 removed PayloadCarryingRpcController, breaking compilation of > MetadataRpcController, InterRegionServerIndexRpcControllerFactory, > IndexRpcController, ClientRpcControllerFactory, and > InterRegionServerMetadataRpcControllerFactory. This class was annotated as > Private so was fair game to remove. It will be gone in HBase 1.4.x and up. > DelegateRegionObserver needs to implement added interface method > postCommitStoreFile. > DelegateHTable, TephraTransactionTable, and OmidTransactionTable need to > implement added interface methods for getting and setting read and write > timeouts. > PhoenixRpcScheduler needs to implement added interface methods for getting > handler counts. > Store file readers/writers/scanners have been refactored and the local index > implementation, which implements or overrides parts of this refactored > hierarchy will have to also be refactored. > DelegateRegionCoprocessorEnvironment needs to implement added method > getMetricRegistryForRegionServer > Another issue with IndexRpcController: incompatible types: int cannot be > converted to org.apache.hadoop.hbase.TableName -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (PHOENIX-4076) Move master branch up to HBase 1.4.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/PHOENIX-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319461#comment-16319461 ] Lars Hofhansl commented on PHOENIX-4076: And this patch can change 1.4.0-SNAPSHOT to 1.4.0 in pom.xml > Move master branch up to HBase 1.4.0-SNAPSHOT > - > > Key: PHOENIX-4076 > URL: https://issues.apache.org/jira/browse/PHOENIX-4076 > Project: Phoenix > Issue Type: Bug >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Attachments: PHOENIX-4076.patch > > > Move master branch up to HBase 1.4.0-SNAPSHOT. > There are some compilation problems. > Valid compatibility breaks are addressed and fixed by HBASE-18431. This > analysis is a compilation attempt of Phoenix master branch against > 1.4.0-SNAPSHOT artifacts including the HBASE-18431 changes. > HBASE-16584 removed PayloadCarryingRpcController, breaking compilation of > MetadataRpcController, InterRegionServerIndexRpcControllerFactory, > IndexRpcController, ClientRpcControllerFactory, and > InterRegionServerMetadataRpcControllerFactory. This class was annotated as > Private so was fair game to remove. It will be gone in HBase 1.4.x and up. > DelegateRegionObserver needs to implement added interface method > postCommitStoreFile. > DelegateHTable, TephraTransactionTable, and OmidTransactionTable need to > implement added interface methods for getting and setting read and write > timeouts. > PhoenixRpcScheduler needs to implement added interface methods for getting > handler counts. > Store file readers/writers/scanners have been refactored and the local index > implementation, which implements or overrides parts of this refactored > hierarchy will have to also be refactored. > DelegateRegionCoprocessorEnvironment needs to implement added method > getMetricRegistryForRegionServer > Another issue with IndexRpcController: incompatible types: int cannot be > converted to org.apache.hadoop.hbase.TableName -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (PHOENIX-4076) Move master branch up to HBase 1.4.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/PHOENIX-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319475#comment-16319475 ] James Taylor commented on PHOENIX-4076: --- +1 to patch, moving master to 1.4 and creating new 4.x branch for 1.3. As far as dropping branches, please see online discussions as we’ve had RMs step up for 1.2 and 1.1 branches. > Move master branch up to HBase 1.4.0-SNAPSHOT > - > > Key: PHOENIX-4076 > URL: https://issues.apache.org/jira/browse/PHOENIX-4076 > Project: Phoenix > Issue Type: Bug >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Attachments: PHOENIX-4076.patch > > > Move master branch up to HBase 1.4.0-SNAPSHOT. > There are some compilation problems. > Valid compatibility breaks are addressed and fixed by HBASE-18431. This > analysis is a compilation attempt of Phoenix master branch against > 1.4.0-SNAPSHOT artifacts including the HBASE-18431 changes. > HBASE-16584 removed PayloadCarryingRpcController, breaking compilation of > MetadataRpcController, InterRegionServerIndexRpcControllerFactory, > IndexRpcController, ClientRpcControllerFactory, and > InterRegionServerMetadataRpcControllerFactory. This class was annotated as > Private so was fair game to remove. It will be gone in HBase 1.4.x and up. > DelegateRegionObserver needs to implement added interface method > postCommitStoreFile. > DelegateHTable, TephraTransactionTable, and OmidTransactionTable need to > implement added interface methods for getting and setting read and write > timeouts. > PhoenixRpcScheduler needs to implement added interface methods for getting > handler counts. > Store file readers/writers/scanners have been refactored and the local index > implementation, which implements or overrides parts of this refactored > hierarchy will have to also be refactored. > DelegateRegionCoprocessorEnvironment needs to implement added method > getMetricRegistryForRegionServer > Another issue with IndexRpcController: incompatible types: int cannot be > converted to org.apache.hadoop.hbase.TableName -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (PHOENIX-4414) Exception while using database metadata commands on tenant specific connection
[
https://issues.apache.org/jira/browse/PHOENIX-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319477#comment-16319477
]
Hudson commented on PHOENIX-4414:
-
FAILURE: Integrated in Jenkins build Phoenix-master #1910 (See
[https://builds.apache.org/job/Phoenix-master/1910/])
PHOENIX-4414 Exception while using database metadata commands on tenant
(mujtaba: rev 01642d5f948fb01f61e65d1bd58ff2661a8918db)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixDatabaseMetaData.java
* (edit)
phoenix-core/src/it/java/org/apache/phoenix/end2end/QueryDatabaseMetaDataIT.java
> Exception while using database metadata commands on tenant specific connection
> --
>
> Key: PHOENIX-4414
> URL: https://issues.apache.org/jira/browse/PHOENIX-4414
> Project: Phoenix
> Issue Type: Bug
>Reporter: Mujtaba Chohan
>Assignee: Mujtaba Chohan
>Priority: Minor
> Attachments: PHOENIX-4414.patch, PHOENIX-4414_v2.patch
>
>
> This is when using tenant specific connection from Sqlline.
> {noformat}
> Error: ERROR 602 (42P00): Syntax error. Missing "LPAREN" at line 2, column
> 746. (state=42P00,code=602)
> org.apache.phoenix.exception.PhoenixParserException: ERROR 602 (42P00):
> Syntax error. Missing "LPAREN" at line 2, column 746.
> at
> org.apache.phoenix.exception.PhoenixParserException.newException(PhoenixParserException.java:33)
> at org.apache.phoenix.parse.SQLParser.parseStatement(SQLParser.java:111)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$PhoenixStatementParser.parseStatement(PhoenixStatement.java:1529)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.parseStatement(PhoenixStatement.java:1612)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:1653)
> at
> org.apache.phoenix.jdbc.PhoenixDatabaseMetaData.getColumns(PhoenixDatabaseMetaData.java:557)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (PHOENIX-4076) Move master branch up to HBase 1.4.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/PHOENIX-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319488#comment-16319488 ] Lars Hofhansl commented on PHOENIX-4076: [~apurtell], [~jamestaylor], do you want to create the branche and move master forward? (I do not want to step on anybody's toes) > Move master branch up to HBase 1.4.0-SNAPSHOT > - > > Key: PHOENIX-4076 > URL: https://issues.apache.org/jira/browse/PHOENIX-4076 > Project: Phoenix > Issue Type: Bug >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Attachments: PHOENIX-4076.patch > > > Move master branch up to HBase 1.4.0-SNAPSHOT. > There are some compilation problems. > Valid compatibility breaks are addressed and fixed by HBASE-18431. This > analysis is a compilation attempt of Phoenix master branch against > 1.4.0-SNAPSHOT artifacts including the HBASE-18431 changes. > HBASE-16584 removed PayloadCarryingRpcController, breaking compilation of > MetadataRpcController, InterRegionServerIndexRpcControllerFactory, > IndexRpcController, ClientRpcControllerFactory, and > InterRegionServerMetadataRpcControllerFactory. This class was annotated as > Private so was fair game to remove. It will be gone in HBase 1.4.x and up. > DelegateRegionObserver needs to implement added interface method > postCommitStoreFile. > DelegateHTable, TephraTransactionTable, and OmidTransactionTable need to > implement added interface methods for getting and setting read and write > timeouts. > PhoenixRpcScheduler needs to implement added interface methods for getting > handler counts. > Store file readers/writers/scanners have been refactored and the local index > implementation, which implements or overrides parts of this refactored > hierarchy will have to also be refactored. > DelegateRegionCoprocessorEnvironment needs to implement added method > getMetricRegistryForRegionServer > Another issue with IndexRpcController: incompatible types: int cannot be > converted to org.apache.hadoop.hbase.TableName -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (PHOENIX-4076) Move master branch up to HBase 1.4.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/PHOENIX-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319504#comment-16319504 ] Lars Hofhansl commented on PHOENIX-4076: Actually some more changes are needed now. I'll post an updated patch in a few. > Move master branch up to HBase 1.4.0-SNAPSHOT > - > > Key: PHOENIX-4076 > URL: https://issues.apache.org/jira/browse/PHOENIX-4076 > Project: Phoenix > Issue Type: Bug >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Attachments: PHOENIX-4076.patch > > > Move master branch up to HBase 1.4.0-SNAPSHOT. > There are some compilation problems. > Valid compatibility breaks are addressed and fixed by HBASE-18431. This > analysis is a compilation attempt of Phoenix master branch against > 1.4.0-SNAPSHOT artifacts including the HBASE-18431 changes. > HBASE-16584 removed PayloadCarryingRpcController, breaking compilation of > MetadataRpcController, InterRegionServerIndexRpcControllerFactory, > IndexRpcController, ClientRpcControllerFactory, and > InterRegionServerMetadataRpcControllerFactory. This class was annotated as > Private so was fair game to remove. It will be gone in HBase 1.4.x and up. > DelegateRegionObserver needs to implement added interface method > postCommitStoreFile. > DelegateHTable, TephraTransactionTable, and OmidTransactionTable need to > implement added interface methods for getting and setting read and write > timeouts. > PhoenixRpcScheduler needs to implement added interface methods for getting > handler counts. > Store file readers/writers/scanners have been refactored and the local index > implementation, which implements or overrides parts of this refactored > hierarchy will have to also be refactored. > DelegateRegionCoprocessorEnvironment needs to implement added method > getMetricRegistryForRegionServer > Another issue with IndexRpcController: incompatible types: int cannot be > converted to org.apache.hadoop.hbase.TableName -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (PHOENIX-4076) Move master branch up to HBase 1.4.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/PHOENIX-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319504#comment-16319504 ] Lars Hofhansl edited comment on PHOENIX-4076 at 1/10/18 1:15 AM: - Actually some more changes are needed now for PhoenixAccessController and PhoenixMetaDataCoprocessorHost. I'll post an updated patch in a few. was (Author: lhofhansl): Actually some more changes are needed now. I'll post an updated patch in a few. > Move master branch up to HBase 1.4.0-SNAPSHOT > - > > Key: PHOENIX-4076 > URL: https://issues.apache.org/jira/browse/PHOENIX-4076 > Project: Phoenix > Issue Type: Bug >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Attachments: PHOENIX-4076.patch > > > Move master branch up to HBase 1.4.0-SNAPSHOT. > There are some compilation problems. > Valid compatibility breaks are addressed and fixed by HBASE-18431. This > analysis is a compilation attempt of Phoenix master branch against > 1.4.0-SNAPSHOT artifacts including the HBASE-18431 changes. > HBASE-16584 removed PayloadCarryingRpcController, breaking compilation of > MetadataRpcController, InterRegionServerIndexRpcControllerFactory, > IndexRpcController, ClientRpcControllerFactory, and > InterRegionServerMetadataRpcControllerFactory. This class was annotated as > Private so was fair game to remove. It will be gone in HBase 1.4.x and up. > DelegateRegionObserver needs to implement added interface method > postCommitStoreFile. > DelegateHTable, TephraTransactionTable, and OmidTransactionTable need to > implement added interface methods for getting and setting read and write > timeouts. > PhoenixRpcScheduler needs to implement added interface methods for getting > handler counts. > Store file readers/writers/scanners have been refactored and the local index > implementation, which implements or overrides parts of this refactored > hierarchy will have to also be refactored. > DelegateRegionCoprocessorEnvironment needs to implement added method > getMetricRegistryForRegionServer > Another issue with IndexRpcController: incompatible types: int cannot be > converted to org.apache.hadoop.hbase.TableName -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PHOENIX-4076) Move master branch up to HBase 1.4.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/PHOENIX-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4076: --- Attachment: PHOENIX-4076-v2.patch Here you go. > Move master branch up to HBase 1.4.0-SNAPSHOT > - > > Key: PHOENIX-4076 > URL: https://issues.apache.org/jira/browse/PHOENIX-4076 > Project: Phoenix > Issue Type: Bug >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Attachments: PHOENIX-4076-v2.patch, PHOENIX-4076.patch > > > Move master branch up to HBase 1.4.0-SNAPSHOT. > There are some compilation problems. > Valid compatibility breaks are addressed and fixed by HBASE-18431. This > analysis is a compilation attempt of Phoenix master branch against > 1.4.0-SNAPSHOT artifacts including the HBASE-18431 changes. > HBASE-16584 removed PayloadCarryingRpcController, breaking compilation of > MetadataRpcController, InterRegionServerIndexRpcControllerFactory, > IndexRpcController, ClientRpcControllerFactory, and > InterRegionServerMetadataRpcControllerFactory. This class was annotated as > Private so was fair game to remove. It will be gone in HBase 1.4.x and up. > DelegateRegionObserver needs to implement added interface method > postCommitStoreFile. > DelegateHTable, TephraTransactionTable, and OmidTransactionTable need to > implement added interface methods for getting and setting read and write > timeouts. > PhoenixRpcScheduler needs to implement added interface methods for getting > handler counts. > Store file readers/writers/scanners have been refactored and the local index > implementation, which implements or overrides parts of this refactored > hierarchy will have to also be refactored. > DelegateRegionCoprocessorEnvironment needs to implement added method > getMetricRegistryForRegionServer > Another issue with IndexRpcController: incompatible types: int cannot be > converted to org.apache.hadoop.hbase.TableName -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PHOENIX-4076) Move master branch up to HBase 1.4.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/PHOENIX-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4076: --- Attachment: (was: PHOENIX-4076-v2.patch) > Move master branch up to HBase 1.4.0-SNAPSHOT > - > > Key: PHOENIX-4076 > URL: https://issues.apache.org/jira/browse/PHOENIX-4076 > Project: Phoenix > Issue Type: Bug >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Attachments: PHOENIX-4076.patch > > > Move master branch up to HBase 1.4.0-SNAPSHOT. > There are some compilation problems. > Valid compatibility breaks are addressed and fixed by HBASE-18431. This > analysis is a compilation attempt of Phoenix master branch against > 1.4.0-SNAPSHOT artifacts including the HBASE-18431 changes. > HBASE-16584 removed PayloadCarryingRpcController, breaking compilation of > MetadataRpcController, InterRegionServerIndexRpcControllerFactory, > IndexRpcController, ClientRpcControllerFactory, and > InterRegionServerMetadataRpcControllerFactory. This class was annotated as > Private so was fair game to remove. It will be gone in HBase 1.4.x and up. > DelegateRegionObserver needs to implement added interface method > postCommitStoreFile. > DelegateHTable, TephraTransactionTable, and OmidTransactionTable need to > implement added interface methods for getting and setting read and write > timeouts. > PhoenixRpcScheduler needs to implement added interface methods for getting > handler counts. > Store file readers/writers/scanners have been refactored and the local index > implementation, which implements or overrides parts of this refactored > hierarchy will have to also be refactored. > DelegateRegionCoprocessorEnvironment needs to implement added method > getMetricRegistryForRegionServer > Another issue with IndexRpcController: incompatible types: int cannot be > converted to org.apache.hadoop.hbase.TableName -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (PHOENIX-4076) Move master branch up to HBase 1.4.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/PHOENIX-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319516#comment-16319516 ] Andrew Purtell commented on PHOENIX-4076: - +1 Over to you [~lhofhansl] > Move master branch up to HBase 1.4.0-SNAPSHOT > - > > Key: PHOENIX-4076 > URL: https://issues.apache.org/jira/browse/PHOENIX-4076 > Project: Phoenix > Issue Type: Bug >Reporter: Andrew Purtell >Assignee: Lars Hofhansl > Attachments: PHOENIX-4076.patch > > > Move master branch up to HBase 1.4.0-SNAPSHOT. > There are some compilation problems. > Valid compatibility breaks are addressed and fixed by HBASE-18431. This > analysis is a compilation attempt of Phoenix master branch against > 1.4.0-SNAPSHOT artifacts including the HBASE-18431 changes. > HBASE-16584 removed PayloadCarryingRpcController, breaking compilation of > MetadataRpcController, InterRegionServerIndexRpcControllerFactory, > IndexRpcController, ClientRpcControllerFactory, and > InterRegionServerMetadataRpcControllerFactory. This class was annotated as > Private so was fair game to remove. It will be gone in HBase 1.4.x and up. > DelegateRegionObserver needs to implement added interface method > postCommitStoreFile. > DelegateHTable, TephraTransactionTable, and OmidTransactionTable need to > implement added interface methods for getting and setting read and write > timeouts. > PhoenixRpcScheduler needs to implement added interface methods for getting > handler counts. > Store file readers/writers/scanners have been refactored and the local index > implementation, which implements or overrides parts of this refactored > hierarchy will have to also be refactored. > DelegateRegionCoprocessorEnvironment needs to implement added method > getMetricRegistryForRegionServer > Another issue with IndexRpcController: incompatible types: int cannot be > converted to org.apache.hadoop.hbase.TableName -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (PHOENIX-4076) Move master branch up to HBase 1.4.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/PHOENIX-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell reassigned PHOENIX-4076: --- Assignee: Lars Hofhansl (was: Andrew Purtell) > Move master branch up to HBase 1.4.0-SNAPSHOT > - > > Key: PHOENIX-4076 > URL: https://issues.apache.org/jira/browse/PHOENIX-4076 > Project: Phoenix > Issue Type: Bug >Reporter: Andrew Purtell >Assignee: Lars Hofhansl > Attachments: PHOENIX-4076.patch > > > Move master branch up to HBase 1.4.0-SNAPSHOT. > There are some compilation problems. > Valid compatibility breaks are addressed and fixed by HBASE-18431. This > analysis is a compilation attempt of Phoenix master branch against > 1.4.0-SNAPSHOT artifacts including the HBASE-18431 changes. > HBASE-16584 removed PayloadCarryingRpcController, breaking compilation of > MetadataRpcController, InterRegionServerIndexRpcControllerFactory, > IndexRpcController, ClientRpcControllerFactory, and > InterRegionServerMetadataRpcControllerFactory. This class was annotated as > Private so was fair game to remove. It will be gone in HBase 1.4.x and up. > DelegateRegionObserver needs to implement added interface method > postCommitStoreFile. > DelegateHTable, TephraTransactionTable, and OmidTransactionTable need to > implement added interface methods for getting and setting read and write > timeouts. > PhoenixRpcScheduler needs to implement added interface methods for getting > handler counts. > Store file readers/writers/scanners have been refactored and the local index > implementation, which implements or overrides parts of this refactored > hierarchy will have to also be refactored. > DelegateRegionCoprocessorEnvironment needs to implement added method > getMetricRegistryForRegionServer > Another issue with IndexRpcController: incompatible types: int cannot be > converted to org.apache.hadoop.hbase.TableName -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PHOENIX-4076) Move master branch up to HBase 1.4.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/PHOENIX-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4076: --- Attachment: PHOENIX-4076-v2.patch OK... This one changes the release name correctly. > Move master branch up to HBase 1.4.0-SNAPSHOT > - > > Key: PHOENIX-4076 > URL: https://issues.apache.org/jira/browse/PHOENIX-4076 > Project: Phoenix > Issue Type: Bug >Reporter: Andrew Purtell >Assignee: Lars Hofhansl > Attachments: PHOENIX-4076-v2.patch, PHOENIX-4076.patch > > > Move master branch up to HBase 1.4.0-SNAPSHOT. > There are some compilation problems. > Valid compatibility breaks are addressed and fixed by HBASE-18431. This > analysis is a compilation attempt of Phoenix master branch against > 1.4.0-SNAPSHOT artifacts including the HBASE-18431 changes. > HBASE-16584 removed PayloadCarryingRpcController, breaking compilation of > MetadataRpcController, InterRegionServerIndexRpcControllerFactory, > IndexRpcController, ClientRpcControllerFactory, and > InterRegionServerMetadataRpcControllerFactory. This class was annotated as > Private so was fair game to remove. It will be gone in HBase 1.4.x and up. > DelegateRegionObserver needs to implement added interface method > postCommitStoreFile. > DelegateHTable, TephraTransactionTable, and OmidTransactionTable need to > implement added interface methods for getting and setting read and write > timeouts. > PhoenixRpcScheduler needs to implement added interface methods for getting > handler counts. > Store file readers/writers/scanners have been refactored and the local index > implementation, which implements or overrides parts of this refactored > hierarchy will have to also be refactored. > DelegateRegionCoprocessorEnvironment needs to implement added method > getMetricRegistryForRegionServer > Another issue with IndexRpcController: incompatible types: int cannot be > converted to org.apache.hadoop.hbase.TableName -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Re: [ANNOUNCE] New release managers
While we're at it. I'd like to propose creating 4.x-HBase-1.3 branch, and turn master into 4.14-HBase-1.4.You might be able to convince me to be the RM for HBase-1.4, if Andrew does not want to do it. Thanks. -- Lars From: James Taylor To: dev@phoenix.apache.org Sent: Thursday, January 4, 2018 1:42 PM Subject: [ANNOUNCE] New release managers Just a heads up, here's the current list of release managers for the supported HBase branches of our Phoenix releases: HBase 2.0: Josh Elser (elserj at apache dot org) HBase 1.3 (master): Thomas D'Silva (tdsilva at apache dot org) HBase 1.2 (and CDH): Pedro Boado (pedro.boado at gmail dot com) HBase 1.1: Xavier Jodoin (xavier at jodoin dot me) HBase 0.98: Andrew Purtell (apurtell at apache dot org) If you have a question about which branch to check your change into, please @ mention the RM for the branch in question. Obvious, important bug fixes can likely be applied across all branches, but this would still be up to the discretion of the RM - ultimately it's up to the RM to ensure that everything needed for a release is checked in. Thanks to all of you for stepping up! James
[jira] [Assigned] (PHOENIX-4523) phoenix.schema.isNamespaceMappingEnabled problem
[
https://issues.apache.org/jira/browse/PHOENIX-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor reassigned PHOENIX-4523:
-
Assignee: Karan Mehta
> phoenix.schema.isNamespaceMappingEnabled problem
>
>
> Key: PHOENIX-4523
> URL: https://issues.apache.org/jira/browse/PHOENIX-4523
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.13.1
>Reporter: Flavio Pompermaier
>Assignee: Karan Mehta
>
> I'm using Phoenix 4.13 for CDH 5.11.2 parcel and enabling schemas made my
> code unusable.
> I think that this is not a bug of the CDH release, but of all 4.13.x releases.
> I have many parallel Phoenix connections and I always get the following
> exception:
> {code:java}
> Caused by: java.sql.SQLException:
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.hbase.TableExistsException):
> SYSTEM:MUTEX
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl$12.call(ConnectionQueryServicesImpl.java:2492)
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl$12.call(ConnectionQueryServicesImpl.java:2384)
> at
> org.apache.phoenix.util.PhoenixContextExecutor.call(PhoenixContextExecutor.java:76)
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl.init(ConnectionQueryServicesImpl.java:2384)
> at
> org.apache.phoenix.jdbc.PhoenixDriver.getConnectionQueryServices(PhoenixDriver.java:255)
> at
> org.apache.phoenix.jdbc.PhoenixEmbeddedDriver.createConnection(PhoenixEmbeddedDriver.java:150)
> 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:270)
> {code}
> This is caused by the fact that all the times the SYSTEM tables are
> recreated, and this cannot be done simultaneously.
> Trying to debug the issue I found that in
> ConnectionQueryServicesImpl.createSysMutexTable() the call to
> getSystemTableNames() always return an empty array and the SYSTEM:MUTEX
> table is always recreated.
> This because getSystemTableNames() doesn't consider the case when system
> tables have namespace enabled. Right now that method tries to get all tables
> starting with *SYSTEM.\**, while it should try to get the list of *SYSTEM:\**
> tables..
> I hope this could get fixed very soon,
> Flavio
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (PHOENIX-4372) Distribution of Apache Phoenix 4.13 for CDH 5.11.2
[ https://issues.apache.org/jira/browse/PHOENIX-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319710#comment-16319710 ] James Taylor commented on PHOENIX-4372: --- Let's see what [~karanmehta93] discovers - I think we're almost there. Things should start moving again now that the holiday season is finished. > Distribution of Apache Phoenix 4.13 for CDH 5.11.2 > -- > > Key: PHOENIX-4372 > URL: https://issues.apache.org/jira/browse/PHOENIX-4372 > Project: Phoenix > Issue Type: Task >Affects Versions: 4.13.0 >Reporter: Pedro Boado >Assignee: Pedro Boado >Priority: Minor > Labels: cdh > Attachments: PHOENIX-4372-v2.patch, PHOENIX-4372-v3.patch, > PHOENIX-4372-v4.patch, PHOENIX-4372-v5.patch, PHOENIX-4372-v6.patch, > PHOENIX-4372-v7.patch, PHOENIX-4372.patch > > > Changes required on top of branch 4.13-HBase-1.2 for creating a parcel of > Apache Phoenix 4.13.0 for CDH 5.11.2 . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (PHOENIX-4514) A incorrect key object is used in SequenceManager#validateSequences
[
https://issues.apache.org/jira/browse/PHOENIX-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319715#comment-16319715
]
James Taylor commented on PHOENIX-4514:
---
Thanks for the JIRA, [~chia7712]. Would you be up for providing a patch?
> A incorrect key object is used in SequenceManager#validateSequences
> ---
>
> Key: PHOENIX-4514
> URL: https://issues.apache.org/jira/browse/PHOENIX-4514
> Project: Phoenix
> Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Priority: Minor
> Fix For: 4.13.0, 5.0.0
>
>
> nextSequences.get( i ) -> nextSequences.get( i ).getSequenceKey()
> {code:title=SequenceManager.java}
> for (int i = 0; i < nextSequences.size(); i++) {
> sequencePosition[i] =
> sequenceMap.get(nextSequences.get(i)).getIndex();
> }
> {code}
> It won't cause bug since the impl of SequenceAllocation#hashCode is equal
> with SequenceKey#hashCode. However, it still a potential bug so a fix is
> necessary I believe.
> {code:title=SequenceAllocation.java}
> @Override
> public int hashCode() {
> return sequenceKey.hashCode();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (PHOENIX-4522) Fail to remove the schema from client-side cache
[
https://issues.apache.org/jira/browse/PHOENIX-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-4522:
--
Fix Version/s: (was: 4.13.0)
4.13.2-cdh5.11.2
4.13.2
4.14.0
> Fail to remove the schema from client-side cache
>
>
> Key: PHOENIX-4522
> URL: https://issues.apache.org/jira/browse/PHOENIX-4522
> Project: Phoenix
> Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Priority: Critical
> Fix For: 5.0.0, 4.14.0, 4.13.2, 4.13.2-cdh5.11.2
>
> Attachments: PHOENIX-4522.v0.patch
>
>
> We always pass the wrong key to remove the schema
> {code:PMetaDataImpl.java}
> @Override
> public void removeSchema(PSchema schema, long schemaTimeStamp) {
>
> this.metaData.schemas.remove(SchemaUtil.getSchemaKey(schema.getSchemaName()));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (PHOENIX-4522) Fail to remove the schema from client-side cache
[
https://issues.apache.org/jira/browse/PHOENIX-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319719#comment-16319719
]
James Taylor commented on PHOENIX-4522:
---
Nice find, [~chia7712]. I'll make sure this gets committed.
> Fail to remove the schema from client-side cache
>
>
> Key: PHOENIX-4522
> URL: https://issues.apache.org/jira/browse/PHOENIX-4522
> Project: Phoenix
> Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Priority: Critical
> Fix For: 5.0.0, 4.14.0, 4.13.2, 4.13.2-cdh5.11.2
>
> Attachments: PHOENIX-4522.v0.patch
>
>
> We always pass the wrong key to remove the schema
> {code:PMetaDataImpl.java}
> @Override
> public void removeSchema(PSchema schema, long schemaTimeStamp) {
>
> this.metaData.schemas.remove(SchemaUtil.getSchemaKey(schema.getSchemaName()));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (PHOENIX-4522) Fail to remove the schema from client-side cache
[
https://issues.apache.org/jira/browse/PHOENIX-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor reassigned PHOENIX-4522:
-
Assignee: Chia-Ping Tsai
> Fail to remove the schema from client-side cache
>
>
> Key: PHOENIX-4522
> URL: https://issues.apache.org/jira/browse/PHOENIX-4522
> Project: Phoenix
> Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Critical
> Fix For: 5.0.0, 4.14.0, 4.13.2, 4.13.2-cdh5.11.2
>
> Attachments: PHOENIX-4522.v0.patch
>
>
> We always pass the wrong key to remove the schema
> {code:PMetaDataImpl.java}
> @Override
> public void removeSchema(PSchema schema, long schemaTimeStamp) {
>
> this.metaData.schemas.remove(SchemaUtil.getSchemaKey(schema.getSchemaName()));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (PHOENIX-4514) A incorrect key object is used in SequenceManager#validateSequences
[
https://issues.apache.org/jira/browse/PHOENIX-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor reassigned PHOENIX-4514:
-
Assignee: Chia-Ping Tsai
> A incorrect key object is used in SequenceManager#validateSequences
> ---
>
> Key: PHOENIX-4514
> URL: https://issues.apache.org/jira/browse/PHOENIX-4514
> Project: Phoenix
> Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Minor
>
> nextSequences.get( i ) -> nextSequences.get( i ).getSequenceKey()
> {code:title=SequenceManager.java}
> for (int i = 0; i < nextSequences.size(); i++) {
> sequencePosition[i] =
> sequenceMap.get(nextSequences.get(i)).getIndex();
> }
> {code}
> It won't cause bug since the impl of SequenceAllocation#hashCode is equal
> with SequenceKey#hashCode. However, it still a potential bug so a fix is
> necessary I believe.
> {code:title=SequenceAllocation.java}
> @Override
> public int hashCode() {
> return sequenceKey.hashCode();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (PHOENIX-4514) A incorrect key object is used in SequenceManager#validateSequences
[
https://issues.apache.org/jira/browse/PHOENIX-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-4514:
--
Fix Version/s: (was: 5.0.0)
(was: 4.13.0)
> A incorrect key object is used in SequenceManager#validateSequences
> ---
>
> Key: PHOENIX-4514
> URL: https://issues.apache.org/jira/browse/PHOENIX-4514
> Project: Phoenix
> Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Minor
>
> nextSequences.get( i ) -> nextSequences.get( i ).getSequenceKey()
> {code:title=SequenceManager.java}
> for (int i = 0; i < nextSequences.size(); i++) {
> sequencePosition[i] =
> sequenceMap.get(nextSequences.get(i)).getIndex();
> }
> {code}
> It won't cause bug since the impl of SequenceAllocation#hashCode is equal
> with SequenceKey#hashCode. However, it still a potential bug so a fix is
> necessary I believe.
> {code:title=SequenceAllocation.java}
> @Override
> public int hashCode() {
> return sequenceKey.hashCode();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (PHOENIX-4514) A incorrect key object is used in SequenceManager#validateSequences
[
https://issues.apache.org/jira/browse/PHOENIX-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319715#comment-16319715
]
James Taylor edited comment on PHOENIX-4514 at 1/10/18 5:39 AM:
Thanks for the JIRA, [~chia7712]. Would you be up for providing a patch? Also,
the fixVersion field is set after the fix is committed to indicate the release
in which the fix will appear.
was (Author: jamestaylor):
Thanks for the JIRA, [~chia7712]. Would you be up for providing a patch?
> A incorrect key object is used in SequenceManager#validateSequences
> ---
>
> Key: PHOENIX-4514
> URL: https://issues.apache.org/jira/browse/PHOENIX-4514
> Project: Phoenix
> Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Minor
>
> nextSequences.get( i ) -> nextSequences.get( i ).getSequenceKey()
> {code:title=SequenceManager.java}
> for (int i = 0; i < nextSequences.size(); i++) {
> sequencePosition[i] =
> sequenceMap.get(nextSequences.get(i)).getIndex();
> }
> {code}
> It won't cause bug since the impl of SequenceAllocation#hashCode is equal
> with SequenceKey#hashCode. However, it still a potential bug so a fix is
> necessary I believe.
> {code:title=SequenceAllocation.java}
> @Override
> public int hashCode() {
> return sequenceKey.hashCode();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (PHOENIX-4514) A incorrect key object is used in SequenceManager#validateSequences
[
https://issues.apache.org/jira/browse/PHOENIX-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319723#comment-16319723
]
Chia-Ping Tsai commented on PHOENIX-4514:
-
bq. Would you be up for providing a patch?
sure
bq. Also, the fixVersion field is set after the fix is committed to indicate
the release in which the fix will appear.
Thanks for the reminder.
> A incorrect key object is used in SequenceManager#validateSequences
> ---
>
> Key: PHOENIX-4514
> URL: https://issues.apache.org/jira/browse/PHOENIX-4514
> Project: Phoenix
> Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Minor
>
> nextSequences.get( i ) -> nextSequences.get( i ).getSequenceKey()
> {code:title=SequenceManager.java}
> for (int i = 0; i < nextSequences.size(); i++) {
> sequencePosition[i] =
> sequenceMap.get(nextSequences.get(i)).getIndex();
> }
> {code}
> It won't cause bug since the impl of SequenceAllocation#hashCode is equal
> with SequenceKey#hashCode. However, it still a potential bug so a fix is
> necessary I believe.
> {code:title=SequenceAllocation.java}
> @Override
> public int hashCode() {
> return sequenceKey.hashCode();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (PHOENIX-4523) phoenix.schema.isNamespaceMappingEnabled problem
[
https://issues.apache.org/jira/browse/PHOENIX-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319725#comment-16319725
]
Karan Mehta commented on PHOENIX-4523:
--
[~f.pompermaier] Can you post the complete stack trace?
Also, {{getSystemTableNames()}} is meant to find SYSTEM tables in default
namespace, which can be migrated to SYSTEM namespace. Hence that is by design.
However we need to see the exact reason behind this issue.
Can you put up more details as follows
1. Is the code unable to start completely or it just throws this exception all
the time is the problem?
2. Any easy way to reproduce the bug, so that I can test locally.
> phoenix.schema.isNamespaceMappingEnabled problem
>
>
> Key: PHOENIX-4523
> URL: https://issues.apache.org/jira/browse/PHOENIX-4523
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.13.1
>Reporter: Flavio Pompermaier
>Assignee: Karan Mehta
>
> I'm using Phoenix 4.13 for CDH 5.11.2 parcel and enabling schemas made my
> code unusable.
> I think that this is not a bug of the CDH release, but of all 4.13.x releases.
> I have many parallel Phoenix connections and I always get the following
> exception:
> {code:java}
> Caused by: java.sql.SQLException:
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.hbase.TableExistsException):
> SYSTEM:MUTEX
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl$12.call(ConnectionQueryServicesImpl.java:2492)
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl$12.call(ConnectionQueryServicesImpl.java:2384)
> at
> org.apache.phoenix.util.PhoenixContextExecutor.call(PhoenixContextExecutor.java:76)
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl.init(ConnectionQueryServicesImpl.java:2384)
> at
> org.apache.phoenix.jdbc.PhoenixDriver.getConnectionQueryServices(PhoenixDriver.java:255)
> at
> org.apache.phoenix.jdbc.PhoenixEmbeddedDriver.createConnection(PhoenixEmbeddedDriver.java:150)
> 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:270)
> {code}
> This is caused by the fact that all the times the SYSTEM tables are
> recreated, and this cannot be done simultaneously.
> Trying to debug the issue I found that in
> ConnectionQueryServicesImpl.createSysMutexTable() the call to
> getSystemTableNames() always return an empty array and the SYSTEM:MUTEX
> table is always recreated.
> This because getSystemTableNames() doesn't consider the case when system
> tables have namespace enabled. Right now that method tries to get all tables
> starting with *SYSTEM.\**, while it should try to get the list of *SYSTEM:\**
> tables..
> I hope this could get fixed very soon,
> Flavio
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (PHOENIX-4523) phoenix.schema.isNamespaceMappingEnabled problem
[
https://issues.apache.org/jira/browse/PHOENIX-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319725#comment-16319725
]
Karan Mehta edited comment on PHOENIX-4523 at 1/10/18 5:56 AM:
---
[~f.pompermaier] Can you post the complete stack trace?
Also, {{getSystemTableNames()}} is meant to find SYSTEM tables in default
namespace, which can be migrated to SYSTEM namespace. Hence that is by design.
However we need to see the exact reason behind this issue.
Can you put up more details as follows
1. Is the code unable to start completely or it just throws this exception all
the time is the problem?
2. Any easy way to reproduce the bug, so that I can test locally.
3. The exact Phoenix version that you are currently using.
4. Is this running on a fresh cluster or a cluster where SYSTEM tables are
already present and are being migrated when the first client connects?
Thanks!
was (Author: karanmehta93):
[~f.pompermaier] Can you post the complete stack trace?
Also, {{getSystemTableNames()}} is meant to find SYSTEM tables in default
namespace, which can be migrated to SYSTEM namespace. Hence that is by design.
However we need to see the exact reason behind this issue.
Can you put up more details as follows
1. Is the code unable to start completely or it just throws this exception all
the time is the problem?
2. Any easy way to reproduce the bug, so that I can test locally.
> phoenix.schema.isNamespaceMappingEnabled problem
>
>
> Key: PHOENIX-4523
> URL: https://issues.apache.org/jira/browse/PHOENIX-4523
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.13.1
>Reporter: Flavio Pompermaier
>Assignee: Karan Mehta
>
> I'm using Phoenix 4.13 for CDH 5.11.2 parcel and enabling schemas made my
> code unusable.
> I think that this is not a bug of the CDH release, but of all 4.13.x releases.
> I have many parallel Phoenix connections and I always get the following
> exception:
> {code:java}
> Caused by: java.sql.SQLException:
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.hbase.TableExistsException):
> SYSTEM:MUTEX
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl$12.call(ConnectionQueryServicesImpl.java:2492)
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl$12.call(ConnectionQueryServicesImpl.java:2384)
> at
> org.apache.phoenix.util.PhoenixContextExecutor.call(PhoenixContextExecutor.java:76)
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl.init(ConnectionQueryServicesImpl.java:2384)
> at
> org.apache.phoenix.jdbc.PhoenixDriver.getConnectionQueryServices(PhoenixDriver.java:255)
> at
> org.apache.phoenix.jdbc.PhoenixEmbeddedDriver.createConnection(PhoenixEmbeddedDriver.java:150)
> 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:270)
> {code}
> This is caused by the fact that all the times the SYSTEM tables are
> recreated, and this cannot be done simultaneously.
> Trying to debug the issue I found that in
> ConnectionQueryServicesImpl.createSysMutexTable() the call to
> getSystemTableNames() always return an empty array and the SYSTEM:MUTEX
> table is always recreated.
> This because getSystemTableNames() doesn't consider the case when system
> tables have namespace enabled. Right now that method tries to get all tables
> starting with *SYSTEM.\**, while it should try to get the list of *SYSTEM:\**
> tables..
> I hope this could get fixed very soon,
> Flavio
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
