-
Notifications
You must be signed in to change notification settings - Fork 34
schema.xml missing fields #74
Comments
Yeah, those are definitely all needed, a PR would be welcome. Thanks for putting this through its paces, we haven't tried to stand up an instance really since building it. |
Not a problem. I'm working on settings this up for myself and will see it through until I'm done. What's the easiest way for you guys to look through these changes? Issues/PR for each change? Or one big one? Just noticed another missing field (I'll add it in, just dropping it here for posterity.
|
Separate PRs would be preferable, but If it's too much trouble to branch |
Sure! I can split it up. I didn't think it would be this many changes initially so I just kept committing to master but I can see how its quickly becoming unwieldy if you want to reject anything. I had a couple questions regarding getting set up, do you have a preferred method of contact? Github has your email as [email protected]. |
Yep that email will work just fine. |
When I symlinked solr/schema.xml to my lucene database and tried to ingest a sample document it would error out on several missing fields:
Should I open a PR and add them in?
P.S. Also the solr version I was using required me to have this field
The text was updated successfully, but these errors were encountered: