[
https://issues.apache.org/jira/browse/PHOENIX-6843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-6843:
---------------------------------
Description:
I see failures on fast machines that seem to be because we're specifying the
current timestamp as CurrentSCN, which actually filters data that is inserted
at the current timestamp.
We should use now()+1 as the CurrentSCN in these cases.
was:
I see failures on fast machines that seem to be because we're specify the
current timestamp as SCN, which actually filters data that is inserted at the
current timestamp.
We should use now()+1 as the CurrentSCN.
> Flakey ViewTTLIT
> ----------------
>
> Key: PHOENIX-6843
> URL: https://issues.apache.org/jira/browse/PHOENIX-6843
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.2.0, 5.1.3
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
>
> I see failures on fast machines that seem to be because we're specifying the
> current timestamp as CurrentSCN, which actually filters data that is inserted
> at the current timestamp.
> We should use now()+1 as the CurrentSCN in these cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
