[
https://issues.apache.org/jira/browse/HADOOP-14144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Fabbri updated HADOOP-14144:
----------------------------------
Attachment: HADOOP-14144-HADOOP-13345.002.patch
This looks good to me. +1.
If you'll indulge me, I've posted a v2 patch that adds some user feedback for
the import function (number of items inserted):
{noformat}
$ hadoop s3guard import -meta dynamodb://mytable -region us-west-2
s3a://mybucket
Inserted 3 items into Metadata Store
{noformat}
I'm fine with your v1 patch, [~mackrorysd], but if you like this one I will
commit the v2.
> 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
> Attachments: HADOOP-14144-HADOOP-13345.001.patch,
> HADOOP-14144-HADOOP-13345.002.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
