-
Notifications
You must be signed in to change notification settings - Fork 18
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
solr loading #473
Comments
@fils I am trying to run the indexer-graph-solr.py script (that requires a directory of .json files, that was generated from the |
(I am assuming that the |
I was expecting to provide JSON-L files where each line is a JSON file essentially. However, I can chance that. So if I make a directory of JSON files instead this would work? However, I need to be able to read this into Solr, is there a compose file I can use that will set up a Solr instance with the OIH schema? |
mdp2solr.py is irrelevant, don't focus on that. I'm just trying to get to a format I can test load but I really need to be able to run it local so my testing iterations are not so long. |
Just to be clear then.. the current indexer.py (https://github.com/iodepo/oih-ui/blob/main/indexer/indexer.py) is what you currently use to generate the JSON from the JSON-LD at present then. |
If you make a directory of JSON files then indexer-graph-solr.py should work. (understood to ignore mdp2solr) Getting Solr running locally for ODIS might be best through the full Docker process ? https://github.com/iodepo/oih-ui-docker (not sure where Arno put his latest notes for that) Current indexer.py was what I had been using last year to import the JSON-LD from the object store, into Solr. |
Jeff,
First can you confirm you can read the file: output.jsonl in the minio server in the path oih/commons/scratch
This is an old file but I am curious it will load via your script or not and what the errors are.
Working on getting you a more current one to test with but try this one and let me know here the errors.
Doug
The text was updated successfully, but these errors were encountered: