Skip to content

Allow skip bad entries logging during import#9103

Merged
tinwelint merged 2 commits intoneo4j:3.0from
MishaDemianenko:3.0-optional-logging-bad-records
Mar 31, 2017
Merged

Allow skip bad entries logging during import#9103
tinwelint merged 2 commits intoneo4j:3.0from
MishaDemianenko:3.0-optional-logging-bad-records

Conversation

@MishaDemianenko
Copy link
Copy Markdown
Contributor

Introduce new import tool option: skip-bad-entries-logging that will allow to skip logging of all bad entries.
Default value of new option: false

Introduce new import tool option `skip-bad-entries-logging`
to allow skip logging of bad entries.
Copy link
Copy Markdown
Member

@tinwelint tinwelint left a comment

Choose a reason for hiding this comment

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

Great that you also deferred the message string creation, which could be expensive.

+ "about relationships refering to missing nodes. Format errors in input data are "
+ "still treated as errors" ),
SKIP_BAD_ENTRIES_LOGGING ("skip-bad-entries-logging", Boolean.FALSE,
"<true/false>", "Whether or not log bad entries detected during import."),
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Whether or not to skip logging bad entries detected during import

Copy link
Copy Markdown
Member

@tinwelint tinwelint left a comment

Choose a reason for hiding this comment

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

Oh, the little change in the option description

@MishaDemianenko
Copy link
Copy Markdown
Contributor Author

@tinwelint updated :)

@tinwelint tinwelint merged commit 5dc7a0e into neo4j:3.0 Mar 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants