You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Sean Mackrory (JIRA)" <ji...@apache.org> on 2017/03/11 00:01:04 UTC
[jira] [Commented] (HADOOP-14144) s3guard: CLI diff non-empty after
import on new table
[ https://issues.apache.org/jira/browse/HADOOP-14144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905901#comment-15905901 ]
Sean Mackrory commented on HADOOP-14144:
----------------------------------------
I've found that if you have empty directories already in S3, they won't get imported. But because Diff discovers FileStatus objects differently than Import, they will still show up in a diff. I filed HADOOP-14172 for that specific fix to the Import command. There are some other fixes related to this behavior in the Diff command itself that I'll post shortly.
> s3guard: CLI diff non-empty after import on new table
> -----------------------------------------------------
>
> Key: HADOOP-14144
> URL: https://issues.apache.org/jira/browse/HADOOP-14144
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Aaron Fabbri
> Assignee: Sean Mackrory
> Priority: Minor
>
> I expected the following steps to yield zero diff from `hadoop s3guard diff` command.
> (1) hadoop s3guard init ... (create fresh table)
> (2) hadoop s3guard import (fresh table, existing bucket with data in it)
> (3) hadoop s3guard diff ..
> Instead I still get a non-zero diff on step #3. I also noticed some entries are printed twice.
> {noformat}
> dude@computer:~/Code/hadoop$ hadoop s3guard diff -meta dynamodb://dude-dev -region us-west-2 s3a://dude-dev
> S3 D s3a://dude-dev/user/fabbri/test/parentdirdest
> S3 D s3a://dude-dev/user/fabbri/test/parentdirdest
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org