[
https://issues.apache.org/jira/browse/HBASE-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233238#comment-13233238
]
Anoop Sam John commented on HBASE-5564:
---------------------------------------
@Laxman
ImportTsv
{code}
+ // If timestamp option is not specified, use current system time.
+ long timstamp = conf.getLong(TIMESTAMP_CONF_KEY,
System.currentTimeMillis());
+
+ // Set it back to replace invalid timestamp (non-numeric) with current
system time
+ conf.setLong(TIMESTAMP_CONF_KEY, timstamp);
{code}
Doing this will use the same TS across all the mappers. Is this the intention
for this change? So in TsvImporterMapper,
conf.getLong(ImportTsv.TIMESTAMP_CONF_KEY, 0) will always have value to get
from conf.
> Bulkload is discarding duplicate records
> ----------------------------------------
>
> Key: HBASE-5564
> URL: https://issues.apache.org/jira/browse/HBASE-5564
> Project: HBase
> Issue Type: Bug
> Components: mapreduce
> Affects Versions: 0.90.7, 0.92.2, 0.94.0, 0.96.0
> Environment: HBase 0.92
> Reporter: Laxman
> Assignee: Laxman
> Labels: bulkloader
> Attachments: HBASE-5564_trunk.patch
>
>
> Duplicate records are getting discarded when duplicate records exists in same
> input file and more specifically if they exists in same split.
> Duplicate records are considered if the records are from diffrent different
> splits.
> Version under test: HBase 0.92
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira