Data driven mode is different from managed schema. It is unfortunate
that in our example configurations we implemented them together.
Managed schema is about using APIs to read/write schema changes. Not
requiring people to hand edit schema.xml is a good thing, IMO.
Data driven schema uses the man
Got it.
Thank you for clarifying this, I was under impression that I would only be
able to make changes via the API. I will look into this some more.
On Fri, Mar 11, 2016 at 11:51 AM, Shawn Heisey wrote:
> On 3/11/2016 9:28 AM, Nick Vasilyev wrote:
> > Maybe I am missing something, if that is t
On 3/11/2016 9:28 AM, Nick Vasilyev wrote:
> Maybe I am missing something, if that is the case what is the difference
> between data_driven_schema_configs and basic_configs? I thought that the
> only difference was that the data_driven_schema_configs comes with the
> managed schema and the basic_co
Hi Shawn,
Maybe I am missing something, if that is the case what is the difference
between data_driven_schema_configs and basic_configs? I thought that the
only difference was that the data_driven_schema_configs comes with the
managed schema and the basic_configs come with regular?
Also, I haven'
On 3/11/2016 7:01 AM, Nick Vasilyev wrote:
> Is this now the default behavior for basic_configs? I would really like to
> maintain an option to easily create collection with classic schema settings
> without jumping through all of these hoops.
Starting in 5.5, all examples now use the managed sche
