[jira] [Resolved] (OMID-190) Update website for 1.0.2

2020-11-23 Thread Istvan Toth (Jira) 


 [ 
https://issues.apache.org/jira/browse/OMID-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth resolved OMID-190.
--
Fix Version/s: 1.0.3
   Resolution: Fixed

Thanks for the review [~chia7712].

 

> Update website for 1.0.2
> 
>
> Key: OMID-190
> URL: https://issues.apache.org/jira/browse/OMID-190
> Project: Phoenix Omid
>  Issue Type: Improvement
>Affects Versions: 1.0.2
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
> Fix For: 1.0.3
>
>
> The site repo URL has changed, and the download links point to the old repo 
> and relase dirs.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [phoenix-omid] stoty commented on pull request #81: OMID-190 Update website for 1.0.2

2020-11-23 Thread GitBox 


stoty commented on pull request #81:
URL: https://github.com/apache/phoenix-omid/pull/81#issuecomment-732722404


   I'm not sure what to do about the readme, especially about the coveralls 
integration.



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

[GitHub] [phoenix-omid] stoty closed pull request #81: OMID-190 Update website for 1.0.2

2020-11-23 Thread GitBox 


stoty closed pull request #81:
URL: https://github.com/apache/phoenix-omid/pull/81


   



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] [Updated] (PHOENIX-6120) Change IndexMaintainer for SINGLE_CELL_ARRAY_WITH_OFFSETS indexes. Currently it assumes data and index table having the same storage and encoding format.

2020-11-23 Thread Gokcen Iskender (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gokcen Iskender updated PHOENIX-6120:
-
Attachment: (was: PHOENIX-6120.master.002.patch)

> Change IndexMaintainer for SINGLE_CELL_ARRAY_WITH_OFFSETS indexes. Currently 
> it assumes data and index table having the same storage and encoding format.
> -
>
> Key: PHOENIX-6120
> URL: https://issues.apache.org/jira/browse/PHOENIX-6120
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Gokcen Iskender
>Priority: Major
> Attachments: PHOENIX-6120.4.x.001.patch
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> This Jira is a followup Jira of PHOENIX-5923 where data and index might have 
> different storage and encoding formats. IndexMaintainer and protobuf needs to 
> change to handle this. Right now, index maintainer assumes both index and 
> data tables have the same format. The protobuf needs to be changed so that 
> IndexMaintainer knows about the data table storage and encoding formats
> Repro:
>  # Create a table with ONE_CELL_PER_COLUMN storage format
>  # Create an index that has covered columns and the IMMUTABLE_STORAGE_SCHEME 
> is SINGLE_CELL_ARRAY_WITH_OFFSETS
>  # Upsert rows to data table
>  # Query the covered column using index --> Null value is returned even 
> though there is a value. 
> IndexMaintainer has a 4 year old code that doesn't return a value for covered 
> columns,



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (PHOENIX-6120) Change IndexMaintainer for SINGLE_CELL_ARRAY_WITH_OFFSETS indexes. Currently it assumes data and index table having the same storage and encoding format.

2020-11-23 Thread Gokcen Iskender (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gokcen Iskender updated PHOENIX-6120:
-
Attachment: PHOENIX-6120.4.x.001.patch

> Change IndexMaintainer for SINGLE_CELL_ARRAY_WITH_OFFSETS indexes. Currently 
> it assumes data and index table having the same storage and encoding format.
> -
>
> Key: PHOENIX-6120
> URL: https://issues.apache.org/jira/browse/PHOENIX-6120
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Gokcen Iskender
>Priority: Major
> Attachments: PHOENIX-6120.4.x.001.patch
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> This Jira is a followup Jira of PHOENIX-5923 where data and index might have 
> different storage and encoding formats. IndexMaintainer and protobuf needs to 
> change to handle this. Right now, index maintainer assumes both index and 
> data tables have the same format. The protobuf needs to be changed so that 
> IndexMaintainer knows about the data table storage and encoding formats
> Repro:
>  # Create a table with ONE_CELL_PER_COLUMN storage format
>  # Create an index that has covered columns and the IMMUTABLE_STORAGE_SCHEME 
> is SINGLE_CELL_ARRAY_WITH_OFFSETS
>  # Upsert rows to data table
>  # Query the covered column using index --> Null value is returned even 
> though there is a value. 
> IndexMaintainer has a 4 year old code that doesn't return a value for covered 
> columns,



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (PHOENIX-5920) Skip SYSTEM TABLE checks while creating phoenix connection if client has set the DoNotUpgrade config

2020-11-23 Thread Neha Gupta (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neha Gupta updated PHOENIX-5920:

Attachment: PHOENIX-5920.master.patch

> Skip SYSTEM TABLE checks while creating phoenix connection if client has set 
> the DoNotUpgrade config
> 
>
> Key: PHOENIX-5920
> URL: https://issues.apache.org/jira/browse/PHOENIX-5920
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 5.0.0, 4.15.0, 4.14.3
>Reporter: Neha Gupta
>Assignee: Neha Gupta
>Priority: Major
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-5920.4.x.patch, PHOENIX-5920.master.patch, 
> PHOENIX-5920.patch, PHOENIX-5920.v1.patch, PHOENIX-5920.v2.patch, 
> PHOENIX-5920.v3.patch, PHOENIX-5920.v4.patch, PHOENIX-5920.v5.patch
>
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> Phoenix checks upgrade path even if client has set "DoNotUpgrade" config. 
> When HMaster failover happens and Phoenix client creating phoenix connection, 
> we get exception "org.apache.hadoop.hbase.PleaseHoldException: Master is 
> initializing" because phoenix calls HBase admin apis to check if SYSTEM 
> tables are in place and does not require an upgrade.  
> [CQSI.init()|https://github.com/apache/phoenix/blob/aad583670ea821286ab5e2460ce0ab7255d474c4/phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java#L3169]
>  initiates creating systems table and 
> [CQSI.ensureTableCreated|https://github.com/apache/phoenix/blob/aad583670ea821286ab5e2460ce0ab7255d474c4/phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java#L1246]
>  is checking if SYTEM table requires upgrade and calls hbaseAdminApis to 
> perform this operation which fails if HMaster is not running. Can we honor 
> the "DoNotUpgrade" config by client(By making an assumption that SYSTEM table 
> is already up-to-date and phoenix client shouldn't perform any upgrades) and 
> skip this upgrade checks ?
> EnsureTableCreated performs bunch of client-server compatibility checks like:
> 1.SYSTEM.CATALOG exists and its timestamp < MIN_SYSTEM_TABLE_TIMESTAMP
> 2.SYSTEM.CATALOG exists, but client and server-side namespace mapping is 
> enabled so we need to migrate SYSTEM tables to the SYSTEM namespace
> 3.When an end-user uses the vanilla PhoenixDriver to create a connection and 
> a requirement for upgrade is detected. In this case, the user should get a 
> connection on which they are only able to run "EXECUTE UPGRADE".



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (PHOENIX-5895) Leverage WALCellFilter in the SystemCatalogWALEntryFilter to replicate system catalog table

2020-11-23 Thread Geoffrey Jacoby (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Geoffrey Jacoby updated PHOENIX-5895:
-
Fix Version/s: (was: 4.16.1)
   (was: 4.x)
   (was: 5.1.1)
   (was: 5.0.0-alpha)

> Leverage WALCellFilter in the SystemCatalogWALEntryFilter to replicate system 
> catalog table
> ---
>
> Key: PHOENIX-5895
> URL: https://issues.apache.org/jira/browse/PHOENIX-5895
> Project: Phoenix
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 5.0.0-alpha, 4.x
>Reporter: Sandeep Pal
>Assignee: Sandeep Pal
>Priority: Minor
> Fix For: 5.1.0, 4.16.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (PHOENIX-5895) Leverage WALCellFilter in the SystemCatalogWALEntryFilter to replicate system catalog table

2020-11-23 Thread Sandeep Pal (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sandeep Pal updated PHOENIX-5895:
-
Fix Version/s: 4.16.1
   5.1.1

> Leverage WALCellFilter in the SystemCatalogWALEntryFilter to replicate system 
> catalog table
> ---
>
> Key: PHOENIX-5895
> URL: https://issues.apache.org/jira/browse/PHOENIX-5895
> Project: Phoenix
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 5.0.0-alpha, 4.x
>Reporter: Sandeep Pal
>Assignee: Sandeep Pal
>Priority: Minor
> Fix For: 5.0.0-alpha, 5.1.0, 5.1.1, 4.16.0, 4.x, 4.16.1
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (PHOENIX-5895) Leverage WALCellFilter in the SystemCatalogWALEntryFilter to replicate system catalog table

2020-11-23 Thread Sandeep Pal (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sandeep Pal updated PHOENIX-5895:
-
Fix Version/s: 4.16.0
   5.1.0

> Leverage WALCellFilter in the SystemCatalogWALEntryFilter to replicate system 
> catalog table
> ---
>
> Key: PHOENIX-5895
> URL: https://issues.apache.org/jira/browse/PHOENIX-5895
> Project: Phoenix
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 5.0.0-alpha, 4.x
>Reporter: Sandeep Pal
>Assignee: Sandeep Pal
>Priority: Minor
> Fix For: 5.0.0-alpha, 5.1.0, 4.16.0, 4.x
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (PHOENIX-5895) Leverage WALCellFilter in the SystemCatalogWALEntryFilter to replicate system catalog table

2020-11-23 Thread Sandeep Pal (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sandeep Pal resolved PHOENIX-5895.
--
Resolution: Fixed

> Leverage WALCellFilter in the SystemCatalogWALEntryFilter to replicate system 
> catalog table
> ---
>
> Key: PHOENIX-5895
> URL: https://issues.apache.org/jira/browse/PHOENIX-5895
> Project: Phoenix
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 5.0.0-alpha, 4.x
>Reporter: Sandeep Pal
>Assignee: Sandeep Pal
>Priority: Minor
> Fix For: 4.x, 5.0.0-alpha
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (PHOENIX-5895) Leverage WALCellFilter in the SystemCatalogWALEntryFilter to replicate system catalog table

2020-11-23 Thread Sandeep Pal (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sandeep Pal updated PHOENIX-5895:
-
Affects Version/s: 4.x
   5.0.0-alpha

> Leverage WALCellFilter in the SystemCatalogWALEntryFilter to replicate system 
> catalog table
> ---
>
> Key: PHOENIX-5895
> URL: https://issues.apache.org/jira/browse/PHOENIX-5895
> Project: Phoenix
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 5.0.0-alpha, 4.x
>Reporter: Sandeep Pal
>Assignee: Sandeep Pal
>Priority: Minor
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (PHOENIX-5895) Leverage WALCellFilter in the SystemCatalogWALEntryFilter to replicate system catalog table

2020-11-23 Thread Sandeep Pal (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sandeep Pal updated PHOENIX-5895:
-
Fix Version/s: 5.0.0-alpha
   4.x

> Leverage WALCellFilter in the SystemCatalogWALEntryFilter to replicate system 
> catalog table
> ---
>
> Key: PHOENIX-5895
> URL: https://issues.apache.org/jira/browse/PHOENIX-5895
> Project: Phoenix
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 5.0.0-alpha, 4.x
>Reporter: Sandeep Pal
>Assignee: Sandeep Pal
>Priority: Minor
> Fix For: 5.0.0-alpha, 4.x
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (PHOENIX-6232) Same query fails with IllegalArgumentException if part of a join

2020-11-23 Thread Mate Szalay-Beko (Jira) 
Mate Szalay-Beko created PHOENIX-6232:
-

 Summary: Same query fails with IllegalArgumentException if part of 
a join
 Key: PHOENIX-6232
 URL: https://issues.apache.org/jira/browse/PHOENIX-6232
 Project: Phoenix
  Issue Type: Bug
Reporter: Mate Szalay-Beko


We were facing an interesting problem when a more complex query (with inner 
selects in the WHERE clause) succeeds alone, while the same query fails, if it 
is part of a join. I created a test table / query to reproduce the problem:
{code:sql}
DROP TABLE IF EXISTS test;
CREATE TABLE test (
  id INTEGER NOT NULL,
  test_id INTEGER,
  lastchanged TIMESTAMP,
  CONSTRAINT my_pk PRIMARY KEY (id));

UPSERT INTO test VALUES(0, 100, '2000-01-01 00:00:00.0');
UPSERT INTO test VALUES(1, 101, '2000-01-01 00:00:00.0');
UPSERT INTO test VALUES(2, 100, '2011-11-11 11:11:11.0');
{code}

*Query 1:* Example query, running fine in itself:
{code:sql}
SELECT id, test_id, lastchanged FROM test T
WHERE lastchanged = ( SELECT max(lastchanged) FROM test WHERE test_id = 
T.test_id )

Returns:
++-+---+
| ID | TEST_ID |  LASTCHANGED  |
++-+---+
| 1  | 101 | 2000-01-01 01:00:00.0 |
| 2  | 100 | 2011-11-11 12:11:11.0 |
++-+---+
{code}

*Query 2:* Same query fails on the current master branch, when it is part of a 
larger (implicit) join:
{code:sql}
SELECT AAA.*
FROM 
(
  SELECT id, test_id, lastchanged FROM test T
  WHERE lastchanged = ( SELECT max(lastchanged) FROM test WHERE test_id = 
T.test_id )
) as AAA,
(
  SELECT id FROM test
) as BBB
WHERE AAA.id = BBB.id;


java.lang.IllegalArgumentException
at 
org.apache.phoenix.thirdparty.com.google.common.base.Preconditions.checkArgument(Preconditions.java:128)
at 
org.apache.phoenix.compile.TupleProjectionCompiler.createProjectedTable(TupleProjectionCompiler.java:66)
at 
org.apache.phoenix.compile.QueryCompiler.compileSingleFlatQuery(QueryCompiler.java:663)
at 
org.apache.phoenix.compile.QueryCompiler.compileJoinQuery(QueryCompiler.java:404)
at 
org.apache.phoenix.compile.QueryCompiler.compileJoinQuery(QueryCompiler.java:302)
at 
org.apache.phoenix.compile.QueryCompiler.compileSelect(QueryCompiler.java:249)
at 
org.apache.phoenix.compile.QueryCompiler.compile(QueryCompiler.java:176)
at 
org.apache.phoenix.jdbc.PhoenixStatement$ExecutableSelectStatement.compilePlan(PhoenixStatement.java:504)
at 
org.apache.phoenix.jdbc.PhoenixStatement$ExecutableSelectStatement.compilePlan(PhoenixStatement.java:467)
at 
org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:309)
at 
org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:298)
at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
at 
org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:297)
at 
org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:290)
at 
org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:1933)
at sqlline.Commands.executeSingleQuery(Commands.java:1054)
at sqlline.Commands.execute(Commands.java:1003)
at sqlline.Commands.sql(Commands.java:967)
at sqlline.SqlLine.dispatch(SqlLine.java:734)
at sqlline.SqlLine.begin(SqlLine.java:541)
at sqlline.SqlLine.start(SqlLine.java:267)
at sqlline.SqlLine.main(SqlLine.java:206)
{code}
I am not sure what the problem is exactly. My guess is that Phoenix tries to 
optimize (flatten) an inner-query, which it shouldn't, if we are inside a join 
(according to the check in the code which throws the exception).

The best workaround I found was to define an explicit join in the original 
query (Query 1), basically change the inner select into a join. This modified 
query return the same as the original one:


*Query 3:*
{code:sql}
SELECT T.id, T.test_id, T.lastchanged 
FROM 
  test T 
  LEFT JOIN (
SELECT max(lastchanged) AS max_timestamp, 
   test_id AS max_timestamp_test_id
FROM test
GROUP BY test_id
  ) JOIN_TABLE ON JOIN_TABLE.max_timestamp_test_id = T.test_id
WHERE T.lastchanged = JOIN_TABLE.max_timestamp

Returns:
+--+---+---+
| T.ID | T.TEST_ID | T.LASTCHANGED |
+--+---+---+
| 1| 101   | 2000-01-01 01:00:00.0 |
| 2| 100   | 2011-11-11 12:11:11.0 |
+--+---+---+
{code}
*Query 4:* And the same modified query (query 3) now works inside a join:
{code:sql}
SELECT AAA.*
FROM 
(
  SELECT T.id, T.test_id, T.lastchanged 
  FROM 
test T 
LEFT JOIN (
  SELECT max(lastchanged) AS max_timestamp, 
 test_id AS max_timestamp_test_id
  FROM test
  GROUP BY test_id
)

Re: 4.x branch Compile Error When hbase.profile >=1.4

2020-11-23 Thread Viraj Jasani 
PHOENIX-6155 is reopened with an addendum.
Thanks

On Mon, 23 Nov 2020 at 6:14 PM, Viraj Jasani  wrote:

> Thanks for bringing this up. Let me take a look and get back with more
> details.
>
>
> On Mon, 23 Nov 2020 at 4:57 PM, cheng...@apache.org 
> wrote:
>
>> When Compile 4.x with hbase.profile >=1.4, there is following compile
>> error, It may be caused by PHOENIX-6155:
>>
>>
>>
>>
>> phoenix-core/src/test/java/org/apache/phoenix/coprocessor/TaskMetaDataEndpointTest.java:[73,52]
>>  is
>> not abstract and does not override abstract method
>> getMetricRegistryForRegionServer() in
>> org.apache.hadoop.hbase.coprocessor.RegionCoprocessorEnvironment
>
>

[jira] [Updated] (PHOENIX-6155) Prevent doing direct upserts into SYSTEM.TASK from the client

2020-11-23 Thread Viraj Jasani (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viraj Jasani updated PHOENIX-6155:
--
Attachment: PHOENIX-6155.4.x.005addendum.patch

> Prevent doing direct upserts into SYSTEM.TASK from the client
> -
>
> Key: PHOENIX-6155
> URL: https://issues.apache.org/jira/browse/PHOENIX-6155
> Project: Phoenix
>  Issue Type: Improvement
>Affects Versions: 5.0.0, 4.15.0
>Reporter: Chinmay Kulkarni
>Assignee: Viraj Jasani
>Priority: Major
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-6155.4.x.000.patch, PHOENIX-6155.4.x.001.patch, 
> PHOENIX-6155.4.x.002.patch, PHOENIX-6155.4.x.003.patch, 
> PHOENIX-6155.4.x.004.patch, PHOENIX-6155.4.x.005addendum.patch, 
> PHOENIX-6155.master.000.patch
>
>
> In environments with namespace-mapping enabled, we will have to grant write 
> access to clients in order to make direct upserts into SYSTEM.TASK. Currently 
> we add a task from the client-side 
> [here|https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/schema/MetaDataClient.java#L4654].
>  In order to implement other Jiras like 
> [PHOENIX-6154|https://issues.apache.org/jira/browse/PHOENIX-6154] we also may 
> need to interact with the SYSTEM.TASK table from the client-side.
> Instead of doing direct upserts into this table, we should add an endpoint on 
> SYSTEM.TASK and clients should interact with that.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Reopened] (PHOENIX-6155) Prevent doing direct upserts into SYSTEM.TASK from the client

2020-11-23 Thread Viraj Jasani (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viraj Jasani reopened PHOENIX-6155:
---

Reopening for an addendum.

> Prevent doing direct upserts into SYSTEM.TASK from the client
> -
>
> Key: PHOENIX-6155
> URL: https://issues.apache.org/jira/browse/PHOENIX-6155
> Project: Phoenix
>  Issue Type: Improvement
>Affects Versions: 5.0.0, 4.15.0
>Reporter: Chinmay Kulkarni
>Assignee: Viraj Jasani
>Priority: Major
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-6155.4.x.000.patch, PHOENIX-6155.4.x.001.patch, 
> PHOENIX-6155.4.x.002.patch, PHOENIX-6155.4.x.003.patch, 
> PHOENIX-6155.4.x.004.patch, PHOENIX-6155.master.000.patch
>
>
> In environments with namespace-mapping enabled, we will have to grant write 
> access to clients in order to make direct upserts into SYSTEM.TASK. Currently 
> we add a task from the client-side 
> [here|https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/schema/MetaDataClient.java#L4654].
>  In order to implement other Jiras like 
> [PHOENIX-6154|https://issues.apache.org/jira/browse/PHOENIX-6154] we also may 
> need to interact with the SYSTEM.TASK table from the client-side.
> Instead of doing direct upserts into this table, we should add an endpoint on 
> SYSTEM.TASK and clients should interact with that.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: 4.x branch Compile Error When hbase.profile >=1.4

2020-11-23 Thread Viraj Jasani 
Thanks for bringing this up. Let me take a look and get back with more
details.


On Mon, 23 Nov 2020 at 4:57 PM, cheng...@apache.org 
wrote:

> When Compile 4.x with hbase.profile >=1.4, there is following compile
> error, It may be caused by PHOENIX-6155:
>
>
>
>
> phoenix-core/src/test/java/org/apache/phoenix/coprocessor/TaskMetaDataEndpointTest.java:[73,52]
>  is
> not abstract and does not override abstract method
> getMetricRegistryForRegionServer() in
> org.apache.hadoop.hbase.coprocessor.RegionCoprocessorEnvironment

4.x branch Compile Error When hbase.profile >=1.4

2020-11-23 Thread cheng...@apache.org 
When Compile 4.x with hbase.profile >=1.4, there is following compile error, It 
may be caused by PHOENIX-6155:




phoenix-core/src/test/java/org/apache/phoenix/coprocessor/TaskMetaDataEndpointTest.java:[73,52]
  is not 
abstract and does not override abstract method 
getMetricRegistryForRegionServer() in 
org.apache.hadoop.hbase.coprocessor.RegionCoprocessorEnvironment

[jira] [Updated] (PHOENIX-6231) Update Omid to 1.0.2

2020-11-23 Thread Istvan Toth (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth updated PHOENIX-6231:
-
Description: 
Update Omid to 1.0.2

Note that while for master this is a simple update from -SNAPSHOT to final 
version,  for 4.x this includes pulling in phoenix-thirdparty Guava, and the 
same minor code change has master already has.

  was:
Update Omid to 1.0.2

Note that while for master this is a simple update from -SNAPSHOT to final 
version,  for 4.x this includes pulling in phoenix-thirdparty Guava, and the 
same minor code changes has master alterady hase.


> Update Omid to 1.0.2
> 
>
> Key: PHOENIX-6231
> URL: https://issues.apache.org/jira/browse/PHOENIX-6231
> Project: Phoenix
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 5.0.0, 4.16.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
>
> Update Omid to 1.0.2
> Note that while for master this is a simple update from -SNAPSHOT to final 
> version,  for 4.x this includes pulling in phoenix-thirdparty Guava, and the 
> same minor code change has master already has.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (PHOENIX-6231) Update Omid to 1.0.2

2020-11-23 Thread Istvan Toth (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth updated PHOENIX-6231:
-
Description: 
Update Omid to 1.0.2

Note that while for master this is a simple update from -SNAPSHOT to final 
version,  for 4.x this includes pulling in phoenix-thirdparty Guava, and the 
same minor code changes has master alterady hase.

  was:Update Omid to 1.0.2


> Update Omid to 1.0.2
> 
>
> Key: PHOENIX-6231
> URL: https://issues.apache.org/jira/browse/PHOENIX-6231
> Project: Phoenix
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 5.0.0, 4.16.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
>
> Update Omid to 1.0.2
> Note that while for master this is a simple update from -SNAPSHOT to final 
> version,  for 4.x this includes pulling in phoenix-thirdparty Guava, and the 
> same minor code changes has master alterady hase.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (PHOENIX-6231) Update Omid to 1.0.2

2020-11-23 Thread Istvan Toth (Jira) 
Istvan Toth created PHOENIX-6231:


 Summary: Update Omid to 1.0.2
 Key: PHOENIX-6231
 URL: https://issues.apache.org/jira/browse/PHOENIX-6231
 Project: Phoenix
  Issue Type: Improvement
  Components: core
Affects Versions: 5.0.0, 4.16.0
Reporter: Istvan Toth
Assignee: Istvan Toth


Update Omid to 1.0.2



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [phoenix-omid] stoty commented on pull request #81: OMID-190 Update website for 1.0.2

2020-11-23 Thread GitBox 


stoty commented on pull request #81:
URL: https://github.com/apache/phoenix-omid/pull/81#issuecomment-732027448


   Minimum changeset to get the links working.
   No changes in website content otherwise.



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

[GitHub] [phoenix-omid] stoty opened a new pull request #81: OMID-190 Update website for 1.0.2

2020-11-23 Thread GitBox 


stoty opened a new pull request #81:
URL: https://github.com/apache/phoenix-omid/pull/81


   



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] [Created] (OMID-190) Update website for 1.0.2

2020-11-23 Thread Istvan Toth (Jira) 
Istvan Toth created OMID-190:


 Summary: Update website for 1.0.2
 Key: OMID-190
 URL: https://issues.apache.org/jira/browse/OMID-190
 Project: Phoenix Omid
  Issue Type: Improvement
Affects Versions: 1.0.2
Reporter: Istvan Toth
Assignee: Istvan Toth


The site repo URL has changed, and the download links point to the old repo and 
relase dirs.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[ANNOUNCE] Phoenix Omid 1.0.2 released

2020-11-23 Thread Istvan Toth 
Hello Everyone,

The Apache Phoenix team is pleased to announce the immediate
availability of the 1.0.2 release of the Phoenix Omid.


This is the first release of the project by the Apache Phoenix team,
and includes the following improvements:


- Updated Guava and replaced it with the relocated version from
Phoenix Thirdparty to improve compatibility.
- Switched the default timestampType setting to WORLD_TIME

- Minor fixes and build system improvements.


Download source from [1].



Thanks,
Istvan Toth
(on behalf of the Apache Phoenix team)


[1] https://phoenix.apache.org/download.html

[jira] [Assigned] (OMID-153) The method AbstractTransactionManager.closeResources should be protected instead of package private

2020-11-23 Thread Istvan Toth (Jira) 


 [ 
https://issues.apache.org/jira/browse/OMID-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth reassigned OMID-153:


Assignee: Istvan Toth

> The method AbstractTransactionManager.closeResources should be protected 
> instead of package private
> ---
>
> Key: OMID-153
> URL: https://issues.apache.org/jira/browse/OMID-153
> Project: Phoenix Omid
>  Issue Type: Bug
>Affects Versions: 1.0.1
>Reporter: Robert Yokota
>Assignee: Istvan Toth
>Priority: Minor
> Fix For: 1.0.2
>
>
> I was trying to subclass {{AbstractTransactionManager}} from a class in 
> another package, and I was not able to because the method {{closeResources}} 
> is package private instead of protected.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (OMID-153) The method AbstractTransactionManager.closeResources should be protected instead of package private

2020-11-23 Thread Istvan Toth (Jira) 


 [ 
https://issues.apache.org/jira/browse/OMID-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth reassigned OMID-153:


Assignee: (was: Istvan Toth)

> The method AbstractTransactionManager.closeResources should be protected 
> instead of package private
> ---
>
> Key: OMID-153
> URL: https://issues.apache.org/jira/browse/OMID-153
> Project: Phoenix Omid
>  Issue Type: Bug
>Affects Versions: 1.0.1
>Reporter: Robert Yokota
>Priority: Minor
> Fix For: 1.0.2
>
>
> I was trying to subclass {{AbstractTransactionManager}} from a class in 
> another package, and I was not able to because the method {{closeResources}} 
> is package private instead of protected.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (OMID-155) disable trimStackTrace

2020-11-23 Thread Istvan Toth (Jira) 


 [ 
https://issues.apache.org/jira/browse/OMID-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth reassigned OMID-155:


Assignee: Istvan Toth

> disable trimStackTrace
> --
>
> Key: OMID-155
> URL: https://issues.apache.org/jira/browse/OMID-155
> Project: Phoenix Omid
>  Issue Type: Improvement
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
> Fix For: 1.0.2
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> I propose that we disable the trimStackTrace surefire/failsafe option.
> See the identical PHOENIX-5814 for more information.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (OMID-187) Fix incorrect URL of source code

2020-11-23 Thread Istvan Toth (Jira) 


 [ 
https://issues.apache.org/jira/browse/OMID-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth reassigned OMID-187:


Assignee: Chia-Ping Tsai

> Fix incorrect URL of source code
> 
>
> Key: OMID-187
> URL: https://issues.apache.org/jira/browse/OMID-187
> Project: Phoenix Omid
>  Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Trivial
> Fix For: 1.0.2
>
>
> https://git-wip-us.apache.org/repos/asf/incubator-omid.git is not available 
> and the replacement is 
> https://git-wip-us.apache.org/repos/asf/phoenix-omid.git



--
This message was sent by Atlassian Jira
(v8.3.4#803005)