[
https://issues.apache.org/jira/browse/HBASE-26349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kyle Purtell updated HBASE-26349:
----------------------------------------
Description:
Using BufferedMutator wasn't a good idea because we assign client timestamps,
and the store loop is fast enough that on rare occasion two temporally adjacent
URLs in the set of WARCs are equivalent and the timestamp does not advance,
leading later to a rare false positive CORRUPT finding.
While making changes, support direct S3N paths as input paths on the command
line.
was:
Using BufferedMutator wasn't a good idea because we assign client timestamps,
and the store loop is fast enough that on rare occasion two adjacent URLs in a
WARC are equivalent and the timestamp does not advance, leading later to a rare
false positive CORRUPT finding.
While making changes, support direct S3N paths as input paths on the command
line.
> Revert and improve recent change to IntegrationTestLoadCommonCrawl
> ------------------------------------------------------------------
>
> Key: HBASE-26349
> URL: https://issues.apache.org/jira/browse/HBASE-26349
> Project: HBase
> Issue Type: Test
> Components: integration tests, test
> Reporter: Andrew Kyle Purtell
> Assignee: Andrew Kyle Purtell
> Priority: Minor
> Fix For: 2.5.0, 3.0.0-alpha-2
>
>
> Using BufferedMutator wasn't a good idea because we assign client timestamps,
> and the store loop is fast enough that on rare occasion two temporally
> adjacent URLs in the set of WARCs are equivalent and the timestamp does not
> advance, leading later to a rare false positive CORRUPT finding.
> While making changes, support direct S3N paths as input paths on the command
> line.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
