Ran into a 500 server error on LucidWorks 2.0 when checking for “fields” on a collection. It searches fine and I did a little debugging. I am able to retrieve the fields from the url at http://myurl.com:8888/api/collections/TestCrawl1/fields and save it into a file But get a 500 error when selecting it from the admin at: http://myurl.com:8989/collections/TestCrawl1/fields. Any thoughts on where to debug and why this is occurring? It only happens for one collection. This collection was working fine when it was fed in from an external source about 200 documents and now has about 1700 documents. There could be potentially a lot of different meta data fields.
500 server error for fields on just one collection
(4 posts) (2 voices)-
Posted 6 months ago #
-
Hello Kathy-
We apologize for not getting back to you on this before.
I have succeeded in reproducing this. I made a collection with only one document with 10,000 unique dynamic fields. The Solr query browser took tens of seconds to load the entire list. The LWE fields browser timed out.
If you wish to use lots of meta fields, this UI is not designed for that.
Another way to do meta fields is to create a key-value pair in one multi-valued field. In fact, Solr guarantees that data added to multi-valued fields is fetched in the same order as it was added. This allows you to have two multivalued fields, one for the names and the other for the values. This technique also allows you to search for the existence of metafields, even including wildcards. The dynamic fields feature does not allow this.
Posted 5 months ago # -
Found what the problem is. It wasn't due to the number of fields after all although we did trim them down. It was due to one of the metadata names have a period "." in the name of it. Example: dc.language or stuff.example as the name of the meta data. LucidWorks has an issue with displaying it. Also found one where the metadata name was "owner/approved" which also failed (due to the forward slash).
Posted 5 months ago # -
Our apologies for causing you trouble with this. The schema editor API only supports field names with letters, numbers, underscores and hyphens. The UI will not let you create fields with other characters in the name.
This restriction makes many character encoding problems much easier in the LW API and the solr query urls. We do not have a schedule for relaxing the restriction.
Posted 5 months ago #
Reply
You must log in to post.