On 5/2/25 04:10, Jan Høydahl wrote:
Seems you are using the field guessing logic. It is helpful for quick experimentation, as
any text field will have a string equivalent "mytext_str" which can be
immediately used for sorting or faceting, and thus requires *_str to be defined.
It is not a recommended feature to use in production, so disabling it is
adviced. You can instead look at the Schema Designer feature of the Admin UI to
build up your schema.
Note that the guessing logic mutates your schema dynamicaly, so it is not
enough to remove the chain. Your schema will still remain what it was.
The point is that if you start with the default config, that's what you
get. And if you're not "experimenting", it won't bother you unless you
try using child documents.
I'm not sure what you mean by pseudo field and type.
Pseudo-fields is how you do child documents. Dynamic field rules are
based on field type.
Has anyone ever looked at how those two interact?
Dima
