Dummy line about dynamodbtocsv HOT 8 CLOSED

What do you mean, can you run the command and copy out the input and output here?

from dynamodbtocsv.

I run:

node dynamoDBtoCSV.js -t TableName > result.csv

And on the csv i see:

But this 'dummy' line isn't on my dynamoDB its added by the code.

from dynamodbtocsv.

@tcchau can you speak to that? Seems that line wasn't unmarshalled correctly, causing dummy rows to be inserted in its place?

from dynamodbtocsv.

@edasque @MarcoPorracin Hi there. Yes, sorry, I didn't have enough time to solve the original problem completely.

Let me explain: The original problem is that if you have a table that uses a variable set of attributes for items, the first item that is retrieved by dynamoDBtoCSV will define the set of attributes that will be output. That is, if some of your items have an attribute called, 'optionalData', but not the first item, then 'optionalData' from any other item will not be included in the output.

The fastest way for me to resolve this problem was to create a dummy first item that contains every possible attribute that exists in any item in the whole table.

The proper fix would have been to fix the output generation code so that it is aware that we're working with items that may contain additional attributes.

If I have time later on this month, I can work on that, but if someone else can get to it first, by all means!

from dynamodbtocsv.

So @tcchau that line just has to be excluded from the CSV output (or just removed from that doc)?

from dynamodbtocsv.

Yes, @edasque, I just remove it from my CSV output file manually, since I only occasionally run such a report.

from dynamodbtocsv.

@MarcoPorracin @edasque It turns out, upon reviewing the papaparse library documentation a little more closely, there's a way to eliminate the need for the dummy row fairly easily. I've issued a pull request to fix this #32

from dynamodbtocsv.

Fixed on pull request #32

from dynamodbtocsv.