[
https://issues.apache.org/jira/browse/PHOENIX-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011763#comment-15011763
]
James Taylor edited comment on PHOENIX-2429 at 11/18/15 7:37 PM:
-----------------------------------------------------------------
Agreed - makes more sense to standardize on PhoenixRuntime.CURRENT_SCN_ATTRIB.
As far as CurrentSCN being different for input versus output, that's a good
point. Can we follow the same mechanism as we did to set the output cluster to
be different than the input cluster? Was that by allowing an output URL - not
sure I remember the exact mechanism? In that case, we might need a may of
expressing that we don't want a CurrentSCN on the output - maybe by setting
CurrentSCN to a negative value in the URL? Or to a string like "none" or "null"?
was (Author: jamestaylor):
Agreed - makes more sense to standardize on PhoenixRuntime.CURRENT_SCN_ATTRIB.
> PhoenixConfigurationUtil.CURRENT_SCN_VALUE for phoenix-spark plugin does not
> work
> ---------------------------------------------------------------------------------
>
> Key: PHOENIX-2429
> URL: https://issues.apache.org/jira/browse/PHOENIX-2429
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.2.0, 4.6.0
> Reporter: Diego Fustes Villadóniga
>
> When I call the method saveToPhoenix to store the contents of a ProductDD,
> passing a hadoop configuration, where I set
> PhoenixConfigurationUtil.CURRENT_SCN_VALUE to be a given timestamp, the
> values are not stored with such timestamp, but using the server time
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
