[jira] [Created] (OMID-200) Omid client cannot use kerberos cache when using proxyUser
Istvan Toth created OMID-200: Summary: Omid client cannot use kerberos cache when using proxyUser Key: OMID-200 URL: https://issues.apache.org/jira/browse/OMID-200 Project: Phoenix Omid Issue Type: Bug Affects Versions: 1.0.2 Reporter: Istvan Toth Assignee: Istvan Toth The HBase login code with the OMID-199 patch now works for the "normal" case, however, it fails when proxyusers are involved. Effectively, secure connections via Phoenix Query Servers are still not working with Omid. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5850) Set scan id for hbase side log.
[ https://issues.apache.org/jira/browse/PHOENIX-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-5850: --- Fix Version/s: (was: 5.1.0) 5.2.0 > Set scan id for hbase side log. > --- > > Key: PHOENIX-5850 > URL: https://issues.apache.org/jira/browse/PHOENIX-5850 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.14.3 >Reporter: Chen Feng >Assignee: Chen Feng >Priority: Minor > Fix For: 4.14.4, 5.2.0 > > Attachments: PHOENIX-5850-v1.patch > > > Adding scan id can help finding slow queries effectively. > It's helpful for debug and diagnose. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5419) Cleanup anonymous class in TracingQueryPlan
[ https://issues.apache.org/jira/browse/PHOENIX-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-5419: --- Fix Version/s: (was: 5.1.0) 5.2.0 > Cleanup anonymous class in TracingQueryPlan > --- > > Key: PHOENIX-5419 > URL: https://issues.apache.org/jira/browse/PHOENIX-5419 > Project: Phoenix > Issue Type: Sub-task >Reporter: Ankit Jain >Assignee: Ankit Jain >Priority: Minor > Fix For: 5.2.0 > > Attachments: PHOENIX-5419-4.x-HBase-1.3.patch, PHOENIX-5419.patch, > PHOENIX-5419.v2.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Cleanup anonymous class in TracingQueryPlan -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6089) Additional relocations for the 5.1.0 client
[ https://issues.apache.org/jira/browse/PHOENIX-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-6089: --- Fix Version/s: (was: 5.1.0) 5.1.1 > Additional relocations for the 5.1.0 client > --- > > Key: PHOENIX-6089 > URL: https://issues.apache.org/jira/browse/PHOENIX-6089 > Project: Phoenix > Issue Type: Bug >Reporter: Lars Hofhansl >Priority: Major > Fix For: 5.1.1 > > Attachments: 6089-master.txt, 6089.txt > > > I just update the Phoenix connector in Presto locally to work with Phoenix > 5.1.x. > Among other things I relocate a bunch of more classes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6119) UngroupedAggregateRegionObserver Malformed connection url Error thrown when using a zookeeper quorum
[
https://issues.apache.org/jira/browse/PHOENIX-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankit Singhal updated PHOENIX-6119:
---
Fix Version/s: (was: 5.1.0)
5.2.0
> UngroupedAggregateRegionObserver Malformed connection url Error thrown when
> using a zookeeper quorum
>
>
> Key: PHOENIX-6119
> URL: https://issues.apache.org/jira/browse/PHOENIX-6119
> Project: Phoenix
> Issue Type: Bug
> Components: core
>Affects Versions: 5.1.0
>Reporter: Kyle R Stehbens
>Priority: Major
> Fix For: 5.2.0
>
> Attachments: PHOENIX-6119.master.v4.patch
>
>
> When using Phoenix with a HBase instance configured with a HA zookeeper
> quorum URL like the following:
> hbase.zookeeper.quorum='zk1:2181,zk2:2181,zk3:2181'
> Phoenix throws exceptions when trying to collect statistics as follows:
> {noformat}
> 2020-09-09 21:19:45,806 INFO
> [regionserver/regionserver1:16040-shortCompactions-0] util.QueryUtil:
> Creating connection with the jdbc url:
> jdbc:phoenix:zk1:2181,zk2:2181,zk3:2181:2181:/hbase;
> 2020-09-09 21:19:45,808 WARN
> [regionserver/regionserver1:16040-shortCompactions-0]
> coprocessor.UngroupedAggregateRegionObserver: Unable to collect stats for
> test_namespace:test_table
> java.io.IOException: java.sql.SQLException: ERROR 102 (08001): Malformed
> connection url. :zk1:2181,zk2:2181,zk3:2181:2181:/hbase;
> at
> org.apache.phoenix.schema.stats.DefaultStatisticsCollector.init(DefaultStatisticsCollector.java:124)
> at
> org.apache.phoenix.coprocessor.UngroupedAggregateRegionObserver$5.run(UngroupedAggregateRegionObserver.java:1097)
> at
> org.apache.phoenix.coprocessor.UngroupedAggregateRegionObserver$5.run(UngroupedAggregateRegionObserver.java:1082)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1730)
> at org.apache.hadoop.security.SecurityUtil.doAsUser(SecurityUtil.java:517)
> at
> org.apache.hadoop.security.SecurityUtil.doAsLoginUser(SecurityUtil.java:498)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.hbase.util.Methods.call(Methods.java:40)
> at org.apache.hadoop.hbase.security.User.runAsLoginUser(User.java:192)
> at
> org.apache.phoenix.coprocessor.UngroupedAggregateRegionObserver.preCompact(UngroupedAggregateRegionObserver.java:1081)
> at
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$8.call(RegionCoprocessorHost.java:656)
> at
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$8.call(RegionCoprocessorHost.java:652)
> at
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost$ObserverOperationWithResult.callObserver(CoprocessorHost.java:600)
> at
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost.execOperation(CoprocessorHost.java:636)
> at
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost.execOperationWithResult(CoprocessorHost.java:614)
> at
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.preCompact(RegionCoprocessorHost.java:650)
> at
> org.apache.hadoop.hbase.regionserver.compactions.Compactor.postCompactScannerOpen(Compactor.java:288)
> at
> org.apache.hadoop.hbase.regionserver.compactions.Compactor.compact(Compactor.java:317)
> at
> org.apache.hadoop.hbase.regionserver.compactions.DefaultCompactor.compact(DefaultCompactor.java:65)
> at
> org.apache.hadoop.hbase.regionserver.DefaultStoreEngine$DefaultCompactionContext.compact(DefaultStoreEngine.java:126)
> at org.apache.hadoop.hbase.regionserver.HStore.compact(HStore.java:1454)
> at org.apache.hadoop.hbase.regionserver.HRegion.compact(HRegion.java:2260)
> at
> org.apache.hadoop.hbase.regionserver.CompactSplit$CompactionRunner.doCompaction(CompactSplit.java:616)
> at
> org.apache.hadoop.hbase.regionserver.CompactSplit$CompactionRunner.run(CompactSplit.java:658)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.sql.SQLException: ERROR 102 (08001): Malformed connection
> url. :zk1:2181,zk2:2181,zk3:2181:2181:/hbase;
> at
> org.apache.phoenix.exception.SQLExceptionCode$Factory$1.newException(SQLExceptionCode.java:570)
> at
> org.apache.phoenix.exception.SQLExceptionInfo.buildException(SQLExceptionInfo.java:195)
> at
> org.apache.phoenix.
[jira] [Updated] (PHOENIX-6050) Set properties is invalid
[
https://issues.apache.org/jira/browse/PHOENIX-6050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankit Singhal updated PHOENIX-6050:
---
Fix Version/s: (was: 5.1.0)
5.2.0
> Set properties is invalid
> -
>
> Key: PHOENIX-6050
> URL: https://issues.apache.org/jira/browse/PHOENIX-6050
> Project: Phoenix
> Issue Type: Bug
> Components: core
>Affects Versions: 4.13.1, 5.0.0
> Environment: phoenix 4.13.1
> hbase 1.3.1
>Reporter: Chao Wang
>Assignee: Chao Wang
>Priority: Major
> Fix For: 5.2.0
>
> Attachments: PHOENIX-6050.master.001.patch,
> PHOENIX-6050.master.002.patch
>
>
> I set properties in client, which are "phoenix.query.threadPoolSize", but
> this is invalid. ThreadPool always use default value (128).
> code is:
> Properties properties = new Properties();
> properties.setProperty("phoenix.query.threadPoolSize","300");
> PropertiesResolve phoenixpr = new PropertiesResolve();
> String phoenixdriver =
> phoenixpr.readMapByKey("com/main/SyncData.properties", "phoenix_driver");
> String phoenixjdbc = phoenixpr.readMapByKey("com/main/SyncData.properties",
> "phoenix_jdbc");
> Class.forName(phoenixdriver);
> return DriverManager.getConnection(phoenixjdbc,properties);
> throw is:
> Error: Task
> org.apache.phoenix.job.JobManager$InstrumentedJobFutureTask@6e91893 rejected
> from org.apache.phoenix.job.JobManager$1@26ae880a[Running, pool size = 128,
> active threads = 128, queued tasks = 5000, completed tasks = 36647]
> (state=08000,code=101)
> org.apache.phoenix.exception.PhoenixIOException: Task
> org.apache.phoenix.job.JobManager$InstrumentedJobFutureTask@6e91893 rejected
> from org.apache.phoenix.job.JobManager$1@26ae880a[Running, pool size = 128,
> active threads = 128, queued tasks = 5000, completed tasks = 36647]
> at
> org.apache.phoenix.util.ServerUtil.parseServerException(ServerUtil.java:120)
> at
> org.apache.phoenix.iterate.BaseResultIterators.getIterators(BaseResultIterators.java:1024)
> at
> org.apache.phoenix.iterate.BaseResultIterators.getIterators(BaseResultIterators.java:916)
> ^Reason:^
> I find PhoenixDriver create threadpool before init config from properties.
> when create threadpool , config is always default value .
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5894) Table versus Table Full Outer join on Salted tables not working
[ https://issues.apache.org/jira/browse/PHOENIX-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-5894: --- Fix Version/s: (was: 5.1.0) 5.1.1 > Table versus Table Full Outer join on Salted tables not working > --- > > Key: PHOENIX-5894 > URL: https://issues.apache.org/jira/browse/PHOENIX-5894 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 5.0.0 >Reporter: Ben Cohen >Assignee: Rajeshbabu Chintaguntla >Priority: Major > Fix For: 5.1.1, 4.16.1, 4.17.0 > > Attachments: PHOENIX-5894.patch, > Salt_Bucketed_Table_Full_Outer_Join_Issue.docx > > > Trying to do a Full Outer Join on two tables. The operation works when the > tables are not salted but fails with an exception related to casting when > performed on the salted versions of the tables. Here is the exceptions: > "java.lang.ClassCastException: org.apache.phoenix.schema.PColumnImpl cannot > be cast to org.apache.phoenix.schema.ProjectedColumn > at > org.apache.phoenix.compile.JoinCompiler.joinProjectedTables(JoinCompiler.java:1256) > at > org.apache.phoenix.compile.QueryCompiler.compileJoinQuery(QueryCompiler.java:425) > at > org.apache.phoenix.compile.QueryCompiler.compileJoinQuery(QueryCompiler.java:228) > at > org.apache.phoenix.compile.QueryCompiler.compileSelect(QueryCompiler.java:191) > at > org.apache.phoenix.compile.QueryCompiler.compile(QueryCompiler.java:153) > at > org.apache.phoenix.jdbc.PhoenixStatement$ExecutableSelectStatement.compilePlan(PhoenixStatement.java:490) > at > org.apache.phoenix.jdbc.PhoenixStatement$ExecutableSelectStatement.compilePlan(PhoenixStatement.java:456) > at > org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:302) > at > org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:291) > at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53) > at > org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:290) > at > org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:283) > at > org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:1830) > at sqlline.Commands.execute(Commands.java:822) > at sqlline.Commands.sql(Commands.java:732) > at sqlline.SqlLine.dispatch(SqlLine.java:813) > at sqlline.SqlLine.begin(SqlLine.java:686) > at sqlline.SqlLine.start(SqlLine.java:398) > at sqlline.SqlLine.main(SqlLine.java:291)" > I have attached a word document with the complete list of queries and their > results, along with commands to recreate the data. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5750) Upsert on immutable table fails with AccessDeniedException
[
https://issues.apache.org/jira/browse/PHOENIX-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankit Singhal updated PHOENIX-5750:
---
Fix Version/s: (was: 5.1.0)
5.1.1
> Upsert on immutable table fails with AccessDeniedException
> --
>
> Key: PHOENIX-5750
> URL: https://issues.apache.org/jira/browse/PHOENIX-5750
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.15.0, 4.14.3
>Reporter: Swaroopa Kadam
>Assignee: Swaroopa Kadam
>Priority: Major
> Fix For: 5.1.1, 4.16.1, 4.17.0
>
> Attachments: PHOENIX-5750.4.x-HBase-1.3.v1.patch,
> PHOENIX-5750.4.x-HBase-1.3.v2.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {code:java}
> // code placeholder
> In TableDDLPermissionsIT
> @Test
> public void testUpsertIntoImmutableTable() throws Throwable {
> startNewMiniCluster();
> final String schema = "TEST_INDEX_VIEW";
> final String tableName = "TABLE_DDL_PERMISSION_IT";
> final String phoenixTableName = schema + "." + tableName;
> grantSystemTableAccess();
> try {
> superUser1.runAs(new PrivilegedExceptionAction() {
> @Override
> public Void run() throws Exception {
> try {
> verifyAllowed(createSchema(schema), superUser1);
> verifyAllowed(onlyCreateTable(phoenixTableName),
> superUser1);
> } catch (Throwable e) {
> if (e instanceof Exception) {
> throw (Exception)e;
> } else {
> throw new Exception(e);
> }
> }
> return null;
> }
> });
> if (isNamespaceMapped) {
> grantPermissions(unprivilegedUser.getShortName(), schema,
> Action.WRITE, Action.READ,Action.EXEC);
> }
> // we should be able to read the data from another index as well to
> which we have not given any access to
> // this user
> verifyAllowed(upsertRowsIntoTable(phoenixTableName),
> unprivilegedUser);
> } finally {
> revokeAll();
> }
> }
> in BasePermissionsIT:
> AccessTestAction onlyCreateTable(final String tableName) throws SQLException {
> return new AccessTestAction() {
> @Override
> public Object run() throws Exception {
> try (Connection conn = getConnection(); Statement stmt =
> conn.createStatement()) {
> assertFalse(stmt.execute("CREATE IMMUTABLE TABLE " + tableName
> + "(pk INTEGER not null primary key, data VARCHAR,
> val integer)"));
> }
> return null;
> }
> };
> }
> AccessTestAction upsertRowsIntoTable(final String tableName) throws
> SQLException {
> return new AccessTestAction() {
> @Override
> public Object run() throws Exception {
> try (Connection conn = getConnection()) {
> try (PreparedStatement pstmt = conn.prepareStatement(
> "UPSERT INTO " + tableName + " values(?, ?, ?)")) {
> for (int i = 0; i < NUM_RECORDS; i++) {
> pstmt.setInt(1, i);
> pstmt.setString(2, Integer.toString(i));
> pstmt.setInt(3, i);
> assertEquals(1, pstmt.executeUpdate());
> }
> }
> conn.commit();
> }
> return null;
> }
> };
> }{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-6336) Scan filter is incorrectly set to null for index rebuilds
[ https://issues.apache.org/jira/browse/PHOENIX-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-6336: --- Fix Version/s: (was: 4.16.0) (was: 5.1.0) > Scan filter is incorrectly set to null for index rebuilds > - > > Key: PHOENIX-6336 > URL: https://issues.apache.org/jira/browse/PHOENIX-6336 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.1.0, 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6320) support hbase profile param at the release script
[ https://issues.apache.org/jira/browse/PHOENIX-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-6320: --- Fix Version/s: (was: 4.16.0) (was: 5.1.0) > support hbase profile param at the release script > - > > Key: PHOENIX-6320 > URL: https://issues.apache.org/jira/browse/PHOENIX-6320 > Project: Phoenix > Issue Type: New Feature >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Major > > After PHOENIX-6307, we have the ability to release multi-hbase profiles at > one branch, but we need to provide an option for each release run. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6271) Effective DDL generated by SchemaExtractionTool should maintain the order of PK and other columns
[ https://issues.apache.org/jira/browse/PHOENIX-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-6271: --- Fix Version/s: (was: 4.16.0) > Effective DDL generated by SchemaExtractionTool should maintain the order of > PK and other columns > - > > Key: PHOENIX-6271 > URL: https://issues.apache.org/jira/browse/PHOENIX-6271 > Project: Phoenix > Issue Type: Improvement >Reporter: Swaroopa Kadam >Assignee: Swaroopa Kadam >Priority: Minor > > SchemaExtractionTool is used to generate effective DDL which can be then > compared with the DDL on the cluster to perform schema monitoring. > This won't affect the monitoring part but would be good to have the PR order > in place so that effective DDL can be used for creating the entity for the > first time in a new environment. > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6118) Multi Tenant Workloads using PHERF
[ https://issues.apache.org/jira/browse/PHOENIX-6118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-6118: --- Fix Version/s: (was: 4.16.0) > Multi Tenant Workloads using PHERF > -- > > Key: PHOENIX-6118 > URL: https://issues.apache.org/jira/browse/PHOENIX-6118 > Project: Phoenix > Issue Type: Improvement >Reporter: Jacob Isaac >Assignee: Jacob Isaac >Priority: Major > Time Spent: 3h 50m > Remaining Estimate: 0h > > Features like PHOENIX_TTL and Splittable SYSCAT need to be tested for a large > number of tenant views. > In the absence of support for creating a large number of tenant views - Multi > leveled views dynamically and be able to query them in a generic framework, > the teams have to write custom logic to replay/run functional and perf > testing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6334) All map tasks should operate on the same restored snapshot
[ https://issues.apache.org/jira/browse/PHOENIX-6334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-6334: --- Fix Version/s: (was: 4.x) (was: 4.16.0) (was: 5.1.0) > All map tasks should operate on the same restored snapshot > -- > > Key: PHOENIX-6334 > URL: https://issues.apache.org/jira/browse/PHOENIX-6334 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 5.0.0, 4.14.3 >Reporter: Saksham Gangwar >Assignee: Rushabh Shah >Priority: Major > > Recently we switched an MR application from scanning live tables to scanning > snapshots (PHOENIX-3744). We ran into a severe performance issue, which > turned out to a correctness issue due to over-lapping scan splits generation. > After some debugging we figured that it has been fixed via PHOENIX-4997. > We also *need not restore the snapshot per map task*. The purpose of this > Jira is to correct that behavior. Currently, we restore the snapshot once per > map task into a temp directory. For large tables on big clusters, this > creates a storm of NN RPCs. We can do this once per job and let all the map > tasks operate on the same restored snapshot. HBase already did this via > HBASE-18806, we can do something similar. > > All other performance suggestions here: > https://issues.apache.org/jira/browse/PHOENIX-6081 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6190) Race condition in view creation may allow conflicting changes for pre-4.15 clients and for scenarios with phoenix.allow.system.catalog.rollback=true
[ https://issues.apache.org/jira/browse/PHOENIX-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-6190: --- Fix Version/s: (was: 4.16.0) (was: 5.1.0) > Race condition in view creation may allow conflicting changes for pre-4.15 > clients and for scenarios with phoenix.allow.system.catalog.rollback=true > > > Key: PHOENIX-6190 > URL: https://issues.apache.org/jira/browse/PHOENIX-6190 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.0.0, 4.15.0 >Reporter: Chinmay Kulkarni >Priority: Major > > For pre-4.15 clients and in scenarios where > phoenix.allow.system.catalog.rollback=true, we have to block adding/dropping > a column to/from a parent table/view as we no longer lock the parent on the > server side while creating a child view to prevent conflicting changes. This > is handled on the client side from 4.15 onwards. > However, there is a slight race condition here where a view may be created > between the time we find all children of the parent and the time we do this > check (see > [this|https://github.com/apache/phoenix/blob/264310bd1e6c14996c3cfb11557fc66a012cb01b/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/MetaDataEndpointImpl.java#L2592]). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5346) SaltedIndexIT is flapping
[
https://issues.apache.org/jira/browse/PHOENIX-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankit Singhal updated PHOENIX-5346:
---
Fix Version/s: (was: 4.16.0)
(was: 5.1.0)
5.2.0
4.17.0
> SaltedIndexIT is flapping
> -
>
> Key: PHOENIX-5346
> URL: https://issues.apache.org/jira/browse/PHOENIX-5346
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.15.0
>Reporter: Lars Hofhansl
>Priority: Critical
> Labels: disabled-test
> Fix For: 4.17.0, 5.2.0
>
>
> {code}
> [ERROR] Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 14.042 s <<< FAILURE! - in org.apache.phoenix.end2end.index.SaltedIndexIT
> [ERROR]
> testMutableTableIndexMaintanenceSaltedSalted(org.apache.phoenix.end2end.index.SaltedIndexIT)
> Time elapsed: 4.661 s <<< FAILURE!
> org.junit.ComparisonFailure: expected:<[y]> but was:<[x]>
> at
> org.apache.phoenix.end2end.index.SaltedIndexIT.testMutableTableIndexMaintanence(SaltedIndexIT.java:129)
> at
> org.apache.phoenix.end2end.index.SaltedIndexIT.testMutableTableIndexMaintanenceSaltedSalted(SaltedIndexIT.java:74)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5906) Use a recent version of maven-shade-plugin
[ https://issues.apache.org/jira/browse/PHOENIX-5906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-5906: --- Fix Version/s: (was: 4.16.0) 4.17.0 > Use a recent version of maven-shade-plugin > -- > > Key: PHOENIX-5906 > URL: https://issues.apache.org/jira/browse/PHOENIX-5906 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Andrew Kyle Purtell >Assignee: Andrew Kyle Purtell >Priority: Minor > Fix For: 4.17.0 > > Time Spent: 10m > Remaining Estimate: 0h > > The configuration of maven-shade-plugin doesn't require a particular version. > Depending on Maven version, the downloaded plugin may be too old to handle > Java 8 bytecodes, which may come in from Hadoop 3 among other places. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-4878) Remove SharedTableState and replace with PTable
[ https://issues.apache.org/jira/browse/PHOENIX-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-4878: --- Fix Version/s: (was: 4.16.0) 4.17.0 > Remove SharedTableState and replace with PTable > --- > > Key: PHOENIX-4878 > URL: https://issues.apache.org/jira/browse/PHOENIX-4878 > Project: Phoenix > Issue Type: Improvement >Reporter: Thomas D'Silva >Assignee: Xinyi Yan >Priority: Minor > Labels: phoenix-hardening > Fix For: 4.17.0 > > Attachments: PHOENIX-4878.v2-4.x-HBase-1.3.patch, > PHOENIX-4878.v2-master.patch, PHOENIX-4878.v3-4.x-HBase-1.3.patch, > PHOENIX-4878.v3-master.patch, Screenshot from 2019-08-16 10-59-54.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > When we drop a column from a base table we also drop view indexes that > require the column. This information is passed back to the client using the > SharedTableState proto. Convert this to use our regular PTable proto. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6085) Remove duplicate calls to getSysMutexPhysicalTableNameBytes() during the upgrade path
[ https://issues.apache.org/jira/browse/PHOENIX-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-6085: --- Fix Version/s: (was: 4.16.0) (was: 5.1.0) 5.2.0 4.17.0 > Remove duplicate calls to getSysMutexPhysicalTableNameBytes() during the > upgrade path > - > > Key: PHOENIX-6085 > URL: https://issues.apache.org/jira/browse/PHOENIX-6085 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0 >Reporter: Chinmay Kulkarni >Assignee: Richárd Antal >Priority: Minor > Labels: phoenix-hardening, quality-improvement > Fix For: 4.17.0, 5.2.0 > > Attachments: PHOENIX-6085.4.x.v1.patch, PHOENIX-6085.master.v1.patch > > > We already make this call inside > [CQSI.acquireUpgradeMutex()|https://github.com/apache/phoenix/blob/1922895dfe5960dc025709b04acfaf974d3959dc/phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java#L4220] > and then call writeMutexCell() which calls this again > [here|https://github.com/apache/phoenix/blob/1922895dfe5960dc025709b04acfaf974d3959dc/phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java#L4244]. > > We should move this to inside writeMutexCell() itself and throw > UpgradeInProgressException if required there to avoid unnecessary expensive > HBase admin API calls. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6127) Prevent unnecessary HBase admin API calls in ViewUtil.getSystemTableForChildLinks() and act lazily instead
[ https://issues.apache.org/jira/browse/PHOENIX-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-6127: --- Fix Version/s: (was: 4.16.0) (was: 5.1.0) 4.17.0 > Prevent unnecessary HBase admin API calls in > ViewUtil.getSystemTableForChildLinks() and act lazily instead > -- > > Key: PHOENIX-6127 > URL: https://issues.apache.org/jira/browse/PHOENIX-6127 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0 >Reporter: Chinmay Kulkarni >Assignee: Richárd Antal >Priority: Major > Labels: phoenix-hardening, quality-improvement > Fix For: 4.17.0 > > Attachments: PHOENIX-6127.master.v1.patch > > > In order to handle the case of older clients connecting to a 4.16 cluster > that has old metadata (no SYSTEM.CHILD_LINK table yet), we call > ViewUtil.getSystemTableForChildLinks() to figure out whether to use > SYSTEM.CHILD_LINK or SYSTEM.CATALOG to look up parent->child linking rows. > Here we do HBase table existence checks using HBase admin APIs (see > [this|https://github.com/apache/phoenix/blob/e3c7b4bdce2524eb4fd1e7eb0ccd3454fcca81ce/phoenix-core/src/main/java/org/apache/phoenix/util/ViewUtil.java#L265-L269]) > which can be avoided. In almost all cases once we've called this API, we > later go on and retrieve the Table object anyhow so we can instead try to > always get the SYSTEM.CHILD_LINK table and if that fails, try to get > SYSTEM.CATALOG. This will avoid additional admin API calls. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5833) Incorrect results with RVCs and AND operator
[
https://issues.apache.org/jira/browse/PHOENIX-5833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankit Singhal updated PHOENIX-5833:
---
Fix Version/s: (was: 4.16.0)
> Incorrect results with RVCs and AND operator
>
>
> Key: PHOENIX-5833
> URL: https://issues.apache.org/jira/browse/PHOENIX-5833
> Project: Phoenix
> Issue Type: Bug
> Components: core
>Affects Versions: 4.15.0
>Reporter: Bharath Vissapragada
>Assignee: Daniel Wong
>Priority: Critical
> Attachments: PHOENIX-5833.4.x.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Phoenix version: 4.15-HBase-1.5
> -- Create a test table and populate a couple of rows.
> {noformat}
> create table repro_bug(a varchar(10) not null, b varchar(10) not null, c
> varchar(10) not null constraint pk primary key(a, b, c));
> upsert into repro_bug values('abc', 'def', 'RRSQ_IMKKL');
> upsert into repro_bug values('abc', 'def', 'RRS_ZYTDT');
> select * from repro_bug;
> +--+--+-+
> | A | B | C |
> +--+--+-+
> | abc | def | RRSQ_IMKKL |
> | abc | def | RRS_ZYTDT |
> +--+--+-+
> {noformat}
> -- Query 1 - Look for rows where C has a certain prefix - Returns correct
> result
> {noformat}
> select A, B, C from REPRO_BUG where C like 'RRS\\_%';
> +--+--++
> | A | B | C |
> +--+--++
> | abc | def | RRS_ZYTDT |
> +--+--++
> {noformat}
> -- Query 2 - Look for rows where (a, b, c) > first row - Returns correct
> result
> {noformat}
> select A, B, C from REPRO_BUG where (A, B, C) > ('abc', 'def', 'RRSQ_IMKKL')
> +--+--++
> | A | B | C |
> +--+--++
> | abc | def | RRS_ZYTDT |
> +--+--++
> {noformat}
> -- Query 3 - Combine the filters from Query 1 and Query2 - Returns incorrect
> result.. Ideally it should return the same row as above.
> {noformat}
> select A, B, C from REPRO_BUG where (A, B, C) > ('abc', 'def', 'RRSQ_IMKKL')
> AND C like 'RRS\\_%';
> ++++
> | A | B | C |
> ++++
> ++++
> {noformat}
> -- Explain for the above incase someone is interested.
> {noformat}
> explain select A, B, C from REPRO_BUG where (A, B, C) > ('abc', 'def',
> 'RRSQ_IMKKL') AND C like 'RRS\\_%';
> ++-++--+
> | PLAN
>| EST_BYTES_READ | EST_ROWS_READ | EST_INFO_TS |
> ++-++--+
> | CLIENT 1-CHUNK PARALLEL 1-WAY ROUND ROBIN RANGE SCAN OVER REPRO_BUG
> ['abcdef'] - [*] | null| null | null |
> | SERVER FILTER BY FIRST KEY ONLY AND C LIKE 'RRS\_%'
>| null| null | null |
> ++-++--+
> 2 rows selected (0.003 seconds)
> {noformat}
> I'm trying to poke around in the code to figure out the issue but my
> understanding of Phoenix is limited at this point. So creating a bug report
> incase someone can figure this out quickly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6393) Please tidy up Incubator releases
[ https://issues.apache.org/jira/browse/PHOENIX-6393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-6393. Resolution: Fixed > Please tidy up Incubator releases > - > > Key: PHOENIX-6393 > URL: https://issues.apache.org/jira/browse/PHOENIX-6393 > Project: Phoenix > Issue Type: Bug >Reporter: Sebb >Assignee: Ankit Singhal >Priority: Major > > The following directory trees appear to be obsolete, and should be removed > please: > https://dist.apache.org/repos/dist/release/incubator/tephra/ > https://dist.apache.org/repos/dist/dev/incubator/tephra/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6393) Please tidy up Incubator releases
[ https://issues.apache.org/jira/browse/PHOENIX-6393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal reassigned PHOENIX-6393: -- Assignee: Ankit Singhal > Please tidy up Incubator releases > - > > Key: PHOENIX-6393 > URL: https://issues.apache.org/jira/browse/PHOENIX-6393 > Project: Phoenix > Issue Type: Bug >Reporter: Sebb >Assignee: Ankit Singhal >Priority: Major > > The following directory trees appear to be obsolete, and should be removed > please: > https://dist.apache.org/repos/dist/release/incubator/tephra/ > https://dist.apache.org/repos/dist/dev/incubator/tephra/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6391) Please tidy up Incubator releases
[ https://issues.apache.org/jira/browse/PHOENIX-6391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal reassigned PHOENIX-6391: -- Assignee: Ankit Singhal > Please tidy up Incubator releases > - > > Key: PHOENIX-6391 > URL: https://issues.apache.org/jira/browse/PHOENIX-6391 > Project: Phoenix > Issue Type: Bug >Reporter: Sebb >Assignee: Ankit Singhal >Priority: Major > > The following directory trees appear to be obsolete, and should be deleted > please: > https://dist.apache.org/repos/dist/release/incubator/omid/ > https://dist.apache.org/repos/dist/dev/incubator/omid/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6391) Please tidy up Incubator releases
[ https://issues.apache.org/jira/browse/PHOENIX-6391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-6391. Release Note: Done Resolution: Fixed > Please tidy up Incubator releases > - > > Key: PHOENIX-6391 > URL: https://issues.apache.org/jira/browse/PHOENIX-6391 > Project: Phoenix > Issue Type: Bug >Reporter: Sebb >Assignee: Ankit Singhal >Priority: Major > > The following directory trees appear to be obsolete, and should be deleted > please: > https://dist.apache.org/repos/dist/release/incubator/omid/ > https://dist.apache.org/repos/dist/dev/incubator/omid/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [phoenix-omid] chrajeshbabu commented on pull request #89: OMID-198 Replace static ports used for TSO server with random ports i…
chrajeshbabu commented on pull request #89: URL: https://github.com/apache/phoenix-omid/pull/89#issuecomment-785460431 @stoty handled the review comment and fixed the failing test cases. Please take a look. Thanks This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (OMID-198) Replace static ports used for TSO server with random ports in the tests
[
https://issues.apache.org/jira/browse/OMID-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17290547#comment-17290547
]
Rajeshbabu Chintaguntla commented on OMID-198:
--
Now the build is green. [~stoty] please take a look at updated changes at PR.
Thanks.
> Replace static ports used for TSO server with random ports in the tests
> ---
>
> Key: OMID-198
> URL: https://issues.apache.org/jira/browse/OMID-198
> Project: Phoenix Omid
> Issue Type: Bug
>Reporter: Rajeshbabu Chintaguntla
>Assignee: Rajeshbabu Chintaguntla
>Priority: Major
> Fix For: 1.0.3
>
>
> Currently static ports used in the tests which cause testcase failures when
> those ran parallel.
> So better to replace those with random ports.
> {noformat}
> [ERROR]
> testNettyChannelWriting(org.apache.omid.tso.TestTSOChannelHandlerNetty) Time
> elapsed: 0.002 s <<< FAILURE!
> org.jboss.netty.channel.ChannelException: Failed to bind to:
> 0.0.0.0/0.0.0.0:1434
> at
> org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:272)
> at
> org.apache.omid.tso.TSOChannelHandler.reconnect(TSOChannelHandler.java:107)
> at
> org.apache.omid.tso.TestTSOChannelHandlerNetty.testNettyChannelWriting(TestTSOChannelHandlerNetty.java:228)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:104)
> at
> org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:54)
> at
> org.testng.internal.InvokeMethodRunnable.run(InvokeMethodRunnable.java:44)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:444)
> at sun.nio.ch.Net.bind(Net.java:436)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:225)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
> at
> org.jboss.netty.channel.socket.nio.NioServerBoss$RegisterTask.run(NioServerBoss.java:193)
> at
> org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:391)
> at
> org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:315)
> at
> org.jboss.netty.channel.socket.nio.NioServerBoss.run(NioServerBoss.java:42)
> at
> org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
> at
> org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
> ... 3 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
