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
The result of this choice is that they can not be set via the ZMI in the portal_catalog/manage_propertiesForm, because you will get an "invalid name" error. I understand that they can be set via code, as described here.
My use case is a set of several distinct Zope instances connected to a single ES cluster. So each instance needs to have its own index name, and it would be necessary to be able to configure these names TTW.
I have added a few fields to this purpose in interfaces.py, but it would have been easier via ZMI.
The text was updated successfully, but these errors were encountered:
I was wondering why the names for the three customization constants were chosen to have a leading underscore:
https://github.com/collective/collective.elasticsearch/blob/master/collective/elasticsearch/es.py#L27
The result of this choice is that they can not be set via the ZMI in the portal_catalog/manage_propertiesForm, because you will get an "invalid name" error. I understand that they can be set via code, as described here.
My use case is a set of several distinct Zope instances connected to a single ES cluster. So each instance needs to have its own index name, and it would be necessary to be able to configure these names TTW.
I have added a few fields to this purpose in interfaces.py, but it would have been easier via ZMI.
The text was updated successfully, but these errors were encountered: