[jira] [Assigned] (PHOENIX-5580) Wrong values seen when updating a view for a table that has an index

2020-04-10 Thread Sandeep Guggilam (Jira) 


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

Sandeep Guggilam reassigned PHOENIX-5580:
-

Assignee: Sandeep Guggilam  (was: Abhishek Singh Chouhan)

> Wrong values seen when updating a view for a table that has an index
> 
>
> Key: PHOENIX-5580
> URL: https://issues.apache.org/jira/browse/PHOENIX-5580
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.15.0, 4.14.1, 4.14.3
>Reporter: Swaroopa Kadam
>Assignee: Sandeep Guggilam
>Priority: Major
>  Labels: indexing, phoenix-hardening
> Fix For: 5.1.0, 4.15.1
>
>
> {code:sql}
> CREATE TABLE IF NOT EXISTS TEST (ID INTEGER NOT NULL PRIMARY KEY, HOST 
> VARCHAR(10));
> CREATE INDEX I ON TEST(HOST);
> -- create updatable view (equality condition in where clause)
>  CREATE VIEW V1 (col1 INTEGER) AS SELECT * FROM TEST WHERE ID=15;
>  UPSERT INTO V1(ID, HOST, col1) VALUES (15, 'this', 7);
> SELECT * FROM TEST;
> -- Wrong results, but correct results when using the NO_INDEX hint
> {code}



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

[jira] [Updated] (PHOENIX-5804) Implement strong verification with -v ONLY option for old design of secondary indexes

2020-04-10 Thread Swaroopa Kadam (Jira) 


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

Swaroopa Kadam updated PHOENIX-5804:

Attachment: (was: PHOENIX-5804.4.x.v2.patch)

> Implement strong verification with -v ONLY option for old design of secondary 
> indexes
> -
>
> Key: PHOENIX-5804
> URL: https://issues.apache.org/jira/browse/PHOENIX-5804
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: Swaroopa Kadam
>Assignee: Swaroopa Kadam
>Priority: Major
> Attachments: PHOENIX-5804.4.x.v1.patch, PHOENIX-5804.4.x.v3.patch
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Currently, with -v ONLY option we get weak verification i.e. we find out if 
> index row is present or not. It does not provide information on if the values 
> have mismatch when executed with old design.
> We attempt to provide scrutiny like implementation but way faster. The 
> verification will be done only one the latest version of the row.  
> This will help us in quantifying the success of new self-consistent secondary 
> indexes design. 



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

[jira] [Created] (PHOENIX-5832) Pherf Column does not implement HashCode

2020-04-10 Thread Daniel Wong (Jira) 
Daniel Wong created PHOENIX-5832:


 Summary: Pherf Column does not implement HashCode
 Key: PHOENIX-5832
 URL: https://issues.apache.org/jira/browse/PHOENIX-5832
 Project: Phoenix
  Issue Type: Bug
Reporter: Daniel Wong
Assignee: Daniel Wong


During testing of Pherf scenarios found inconsistent results due to no hashcode 
implementation with a overidden equals method.



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