On 6/14/2018 12:10 PM, Terry Steichen wrote:
> I don't disagree at all, but have a basic question: How do you easily
> transition from a system using a dynamic schema to one using a fixed one?
Not sure you need to actually transition. Just remove the config in
solrconfig.xml that causes Solr to
Shawn,
I don't disagree at all, but have a basic question: How do you easily
transition from a system using a dynamic schema to one using a fixed one?
I'm runnning 6.6.0 in cloud mode (only because it's necessary, as I
understand it, to be in cloud mode for the authentication/authorization
to
On 6/11/2018 2:02 PM, Terry Steichen wrote:
> I am using Solr (6.6.0) in the automatic mode (where it discovers
> fields). It's working fine with one exception. The problem is that
> Solr maps the discovered "meta_creation_date" is assigned the type
> TrieDateField.
>
> Unfortunately, that type
On top of that I would not recommend to use the schema-less mode in
production.
That mode is useful for experimenting and prototyping, but with a managed
schema you would have much more control over a production instance.
Regards
-
---
Alessandro Benedetti
Search Consultant, R
Hi,
You can do that via adding the following lines in managed-schema.
After adding the above and re-indexing docs, you will get the result like
following.
{ "responseHeader":{ "status":0, "QTime":0, "params":{ "q":"*:*", "indent":
"on", "wt":"json", "_":"1528772599296"}},
I am using Solr (6.6.0) in the automatic mode (where it discovers
fields). It's working fine with one exception. The problem is that
Solr maps the discovered "meta_creation_date" is assigned the type
TrieDateField.
Unfortunately, that type is limited in a number of ways (like sorting,
