Skip to content

Make neptune-export cross-platform by removing hardcoded line and path separators#202

Closed
drossi750 wants to merge 4 commits into
awslabs:masterfrom
drossi750:master
Closed

Make neptune-export cross-platform by removing hardcoded line and path separators#202
drossi750 wants to merge 4 commits into
awslabs:masterfrom
drossi750:master

Conversation

@drossi750

Copy link
Copy Markdown

Make neptune-export cross-platform by removing hardcoded line and path separators

Signed-off-by: Rossi, Davide Davide.Rossi@hilti.com

Issue #, if available:

Description of changes:

Even though this would run in a linux-like environment like a lambda, developing and running on a Windows machine yields failing tests. There is no change in the behavior of the application, just making sure that the same execution on different OS leads to the same result.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@beebs-systap

Copy link
Copy Markdown
Member

@triggan Can you take a quick look at this one?


CsvPrinterOptions csvPrinterOptions = CsvPrinterOptions.builder().setIncludeTypeDefinitions(includeTypeDefinitions).build();
JsonPrinterOptions jsonPrinterOptions = JsonPrinterOptions.builder().setStrictCardinality(true).build();
JsonPrinterOptions jsonPrinterOptions = JsonPrinterOptions.builder().setStrictCardinality(strictCardinality).build();

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a change to the default behavior of setStrictCardinality(true). Instead of changing the default behavior, can we leave strictCardinality as true and change the parameter to accept --strict-cardinality false instead?

@triggan

triggan commented Jul 20, 2022

Copy link
Copy Markdown
Contributor

I took a look at the committed changes. Everything looks good except for the change in default behavior for JSON formatting for properties with single values. I think adding the ability to remove the square brackets for properties with single properties makes sense and is needed, but we likely need to make that a configurable change versus changing that to be the default. This thinking is based on the fact that neptune-export is a dependency for many other workloads at this point.

@triggan

triggan commented Jan 2, 2026

Copy link
Copy Markdown
Contributor

Moving this PR over to the official neptune-export repo along with some other considerations. aws/neptune-export#193

@triggan triggan closed this Jan 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants