[
https://issues.apache.org/jira/browse/PHOENIX-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011667#comment-15011667
]
maghamravikiran commented on PHOENIX-2429:
------------------------------------------
Apparently, the property "phoenix.mr.currentscn.value" is a key that users can
set before the job starts. We are currently using it in [1]. I agree , we
could rather use 'CurrentSCN' . Curious, would there be any issues if users
wanted to use the CurrentSCN only for the InputConnection during SELECT query
but not for the OutputConnection for an UPSERT query. By setting this value
in Configuration, all Connection objects will respect the SCN property.
[1]
https://github.com/apache/phoenix/blob/master/phoenix-core/src/main/java/org/apache/phoenix/mapreduce/index/PhoenixIndexImportMapper.java#L75
> 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)
