-
Notifications
You must be signed in to change notification settings - Fork 2
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
Comments
@tloubrieu-jpl that limit is on the mappings, iirc? If so, it will be (has been) resolved by the reindexing sweeper. |
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. |
@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). |
Recommend closing, pending @tloubrieu-jpl assent |
Thanks @alexdunnjpl |
💡 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
The text was updated successfully, but these errors were encountered: