[
https://issues.jboss.org/browse/TEIID-3622?page=com.atlassian.jira.plugin...
]
Juraj Duráni commented on TEIID-3622:
-------------------------------------
There was probably some misunderstanding. My assumption was that HBase translator could
rewrite the data. As you said, the assumption is correct. It means that it is a bug and
need to be fixed.
+*Standard behavior:*+
*Queries:*
CREATE TABLE TableA (id integer PRIMARY KEY, name varchar(10));
INSERT INTO TableA (id, name) VALUES (1, 'name1');
INSERT INTO TableA (id, name) VALUES (1, 'name2'); ---> this command will fail
because uniqueness of the PRIMARY KEY would be corrupted
*Table after queries:*
|id|name|
|1|name1|
+*Behavior of the HBase translator:*+
*Queries:*
CREATE TABLE TableA (id integer PRIMARY KEY, name varchar(10));
INSERT INTO TableA (id, name) VALUES (1, 'name1');
INSERT INTO TableA (id, name) VALUES (1, 'name2'); ---> this command will *NOT*
fail and will rewrite the data
*Table after queries:*
|id|name|
|1|name2|
HBase translator - INSERT could rewrite the data
------------------------------------------------
Key: TEIID-3622
URL:
https://issues.jboss.org/browse/TEIID-3622
Project: Teiid
Issue Type: Bug
Affects Versions: 8.7.1.6_2
Environment: Hbase: 1.1.1
Phoenix: 4.5.0-HBase-1.1
Reporter: Juraj Duráni
Assignee: Steven Hawkins
The HBase translator translates INSERT as UPSERT, which is an "alias" for both
INSERT and UPDATE statement. It means, if user issues same INSERT statement twice, no
exception is thrown [1]. I expect that [2] could rewrite the data.
*Additional note*: I was not able to verify my assumption because of
https://issues.jboss.org/browse/TEIID-3619
[1]
INSERT INTO smalla (intkey) VALUES (55) is translated as UPSERT INTO smalla (intkey)
VALUES (55)
http://phoenix.apache.org/language/index.html#upsert_values
[2]
INSERT INTO smalla (intkey, name) VALUES (1, 'name1')
INSERT INTO smalla (intkey, name) VALUES (1, 'name2')
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)