On 1/20/2016 10:17 AM, Prateek Jain J wrote:
What all I could gather from various blogs is, defining schema stops developers
from accidently adding fields to solr. But in my case, I am planning to use
solrj (so, no spelling mistakes). My point is:
1. Is there any advantage like performance or anything else while reading
or writing or querying, if we go schema way?
2. What impact it can have on maintainability of project?
Another thing to keep in mind is, I am pushing documents to solr from some
random/unknown source and they are not getting stored on separate disc (using
solr for indexing and storing). By this what I mean is, re-indexing is not an
option for me. Starting schemaless might give me a quick start for project
but, is there a fine print that is getting missed? Any
inputs/experiences/pointers are welcome.
There is no performance difference. With a managed schema, there is
still a schema file in the config, it just has a different filename and
can be changed remotely. Internally, I am pretty sure that the java
objects are identical.
I personally would not want to have a managed schema or run in
schemaless mode in production. I do not want it to be possible for
anybody else to change the config.
Thanks,
Shawn
