You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, JSON data for our Solr schemas are put directly into the setup scripts. There are two ways we can refactor this:
Put JSON data in a separate file and have different schema files for adding or replacing fields, and allow our bash setup script to take the JSON data as a command line argument. In other words, we have a single setup script but multiple schema data files
Keep JSON data in the bash setup scripts as-is, but support different flags such as "--replace" to replace existing fields or "--add" to add new fields. Here, we have multiple setup scripts for each specific collection (ACL, CORE).
We will also need to update documentation after this is done.
Option 1 seems cleaner to me but would like to hear other opinions @nikhilro@lintool
The text was updated successfully, but these errors were encountered:
Currently, JSON data for our Solr schemas are put directly into the setup scripts. There are two ways we can refactor this:
Put JSON data in a separate file and have different schema files for adding or replacing fields, and allow our bash setup script to take the JSON data as a command line argument. In other words, we have a single setup script but multiple schema data files
Keep JSON data in the bash setup scripts as-is, but support different flags such as "--replace" to replace existing fields or "--add" to add new fields. Here, we have multiple setup scripts for each specific collection (ACL, CORE).
We will also need to update documentation after this is done.
Option 1 seems cleaner to me but would like to hear other opinions @nikhilro @lintool
The text was updated successfully, but these errors were encountered: