Hello Erick, Thank you for your reply.
Unfortunately, yes it is. I work with a company that has a catalog with many new attributes every day, and sometimes the existing ones change. For instance, one attribute may live with the unit for months (e.g. screen_size ="32 cm") and one day my provider change it to an integer (screen_size = 32), making it easier to create ranges. Besides I want my business users to be able to add and edit new features on their products, and my php middle-end app just should communicate with solr without me. We actually work with a solution that works that way (users do everything, the middle-app controls the users' inputs and deals with the back-end), and dealing with the open-source solr is really hard if that essential feature isn't provided... :( That's why I was very happy when Solr 4.4 introduced the add field by the REST API, that works very well, but I was disapointed that any new field couldn't be edited (just "indexed" and "stored" true / false would be amazing) without I have to edit any file. So I really hope this part of the API will soon be completed :) Best regards, Ben -- View this message in context: http://lucene.472066.n3.nabble.com/Update-field-properties-via-Schema-Rest-API-tp4087907p4087951.html Sent from the Solr - User mailing list archive at Nabble.com.
