Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"collection-id" vs "collection_id" in WARCIndexerCommandOptions.java #315

Open
vkush opened this issue Aug 2, 2024 · 0 comments
Open

"collection-id" vs "collection_id" in WARCIndexerCommandOptions.java #315

vkush opened this issue Aug 2, 2024 · 0 comments

Comments

@vkush
Copy link

vkush commented Aug 2, 2024

Since this commit (ad8b1f6#diff-a625377f8366dfa2c9fa0bb0e8b934d44d3d4d628f46a3e5ccc0350fa4cbe4de) was changed a command line input option in WARCIndexerCommandOptions.java for Collection ID - from "collection_id" to "collection-id", see line here

@Option(names = { "-u", "--collection-id" }, description = "Collection ID.")

It is not a big problem, but it brings some unclarity working with other tools (e.g. indexer is also used by SolrWayback), because parameter in Solr config calls "collection_id", see line here

public static final String COLLECTION_ID = "collection_id";

Would it be possible to switch it back to "collection_id" or maybe to use both variants like it was done for "disable_commit" option here below? Or for community is better to keep it like it is?

@Option(names = { "-d", "--disable_commit", "--disable-commit" }, description = "Disable client side commits (speeds up indexing at the cost of flush guarantee).", defaultValue = "false")

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

No branches or pull requests

1 participant