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

Investigate what the number of property per discipline node was at migration time #332

Closed
tloubrieu-jpl opened this issue Oct 22, 2024 · 5 comments

Comments

@tloubrieu-jpl
Copy link
Member

💡 Description

Knowing that there was a limit of 1000 at the time of the migration , I am wondering if we were able to properly migrate all the products or fields.

⚔️ Parent Epic / Related Tickets

No response

@alexdunnjpl
Copy link
Contributor

@tloubrieu-jpl that limit is on the mappings, iirc? If so, it will be (has been) resolved by the reindexing sweeper.

@tloubrieu-jpl
Copy link
Member Author

What I am wondering how logstash was able to import all the products if there was a limit on the number of fields.

We counted the products so we know they were all there. But maybe some fields were skipped... It is an open question.

@alexdunnjpl
Copy link
Contributor

alexdunnjpl commented Nov 20, 2024

@tloubrieu-jpl fields exist in indices, not documents. The documents were migrated (with the index mappings being updated prior to migration), so all the content is there. Field limits will prevent fields >1000 from being included in the index (i.e. from being searchable), but I see no possibility of limited mappings affecting the migration of document content.

If you have a specific reason for thinking that something was missed I'm all ears, but based on the available information there is no open question that I can see.

Any problems associated with field-limits on indices have been resolved by my recent manual runs of the reindexer sweepers, unless the limits were removed prior to their execution (~10 days since the earliest, if I recall correctly).

@alexdunnjpl
Copy link
Contributor

Recommend closing, pending @tloubrieu-jpl assent

@tloubrieu-jpl
Copy link
Member Author

Thanks @alexdunnjpl

@github-project-automation github-project-automation bot moved this from Sprint Backlog to 🏁 Done in B15.1 Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🏁 Done
Development

No branches or pull requests

2 participants