[
https://issues.apache.org/jira/browse/PHOENIX-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011958#comment-15011958
]
Josh Mahonin commented on PHOENIX-2429:
---------------------------------------
I've confirmed that using PhoenixRuntime.CURRENT_SCN_ATTRIB in the
Configuration does set the 'scn' attribute properly for the input and output
Connections used in loading and saving with phoenix-spark.
If that value is hardcoded into the config file and a user wishes to unset it
for a specific job, I have a feeling that at some point a copy constructor will
end up resetting it. In that case, being able to manually set it to "none" or
"null" should prevent that scenario. I think supporting this should be pretty
straight-forward, and as far as I can tell the only parsing of this field
happens here:
https://github.com/apache/phoenix/blob/master/phoenix-core/src/main/java/org/apache/phoenix/util/JDBCUtil.java#L133
> 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)
