[
https://issues.apache.org/jira/browse/PHOENIX-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14145240#comment-14145240
]
James Taylor commented on PHOENIX-1257:
---------------------------------------
[~jeffreyz] - how about if we do the +1 of the timestamp when we resolve a
table that we're selecting from, here in FromCompiler?
{code}
public static ColumnResolver getResolverForQuery(SelectStatement statement,
PhoenixConnection connection)
{code}
It'd take a bit of hackery to push down that we want to +1 in this case only,
but it's doable. I believe that'd be equivalent to what you're doing, since
you're bumping up the ts for a scan.
> Strange behavior wirh "upsert into ... select from ..." with sequences
> ----------------------------------------------------------------------
>
> Key: PHOENIX-1257
> URL: https://issues.apache.org/jira/browse/PHOENIX-1257
> Project: Phoenix
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Priority: Critical
> Attachments: 1257-WIP.txt, 1257-test.txt
>
>
> I have the following scenario:
> create sequence keys;
> create table X (pk unsigned_long primary key, val integer);
> upsert into x values (1,1);
> Followed by repeated:
> upsert into x select next value for keys, val from x;
> This works well until 2048 rows are inserted. The next
> upsert into x select next value for keys, val from x;
> That loops forever inserting more and more rows until it is stopped.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
