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

Demonstrate roundtrip export/import works #2940

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

epugh
Copy link
Contributor

@epugh epugh commented Jan 6, 2025

https://issues.apache.org/jira/browse/SOLR-13689

Description

Trying to understand best ways of round tripping data. Export from one collection and index into another collection. Use our existing tooling as much as possible.

Solution

Starting with a BATS test to demonstrate that bin/solr export and bin/solr post with .json file works.

Tests

BATS.

@github-actions github-actions bot added the documentation Improvements or additions to documentation label Jan 6, 2025
@epugh epugh marked this pull request as ready for review January 10, 2025 12:51
@epugh epugh requested review from janhoy and gerlowskija January 10, 2025 12:51
@epugh
Copy link
Contributor Author

epugh commented Jan 10, 2025

I'd love a plus one on the this before I merge... For a lot of multi step processes, like exporting and importing data, I find modeling them as BATS tests makes them easier to understand in context. I know that moves these BATS tests towards being integration or even system style tests... I suspect that we may need to split the bats tests into system/integration/unit tests in the future..

Copy link
Contributor

@dsmiley dsmiley left a comment

Choose a reason for hiding this comment

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

Cool. Love the how-to nature of a BATS test here.

@@ -1703,7 +1703,8 @@ The default is `\*:*` which will export all documents.
|===
+
Comma separated list of fields to be exported.
By default all fields are fetched.
By default all fields are fetched.
If your schema uses `copyFields` and you are reindex the data, then you probably want to specify exactly which fields are being exported to simplify the import process.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
If your schema uses `copyFields` and you are reindex the data, then you probably want to specify exactly which fields are being exported to simplify the import process.
If your schema uses `copyFields` and you reindex the data, then you probably want to specify exactly which fields are being exported to simplify the import process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants