Hi folks,
I am using solr 8.5.0 in standalone mode and use the CoreAdmin API and
Schema API of solrj to create new core and its fields in managed-schema
Is there any way to add several fields to managed-schema by solrj without
processing each by each?
The following two rows make the job done by
:
>
> I am using Solr 8.3.1 in non-SolrCloud mode (what should I call this mode?)
> and
> modifying managed-schema.
>
> I noticed that Solr does override this file wiping out all my comments and
> rearranging the order. I noticed there is a "DO NOT EDIT" comment. Then
TK Solr :
>
> I am using Solr 8.3.1 in non-SolrCloud mode (what should I call this mode?)
> and modifying managed-schema.
>
> I noticed that Solr does override this file wiping out all my comments and
> rearranging the order. I noticed there is a "DO NOT EDIT" comme
I am using Solr 8.3.1 in non-SolrCloud mode (what should I call this mode?) and
modifying managed-schema.
I noticed that Solr does override this file wiping out all my comments and
rearranging the order. I noticed there is a "DO NOT EDIT" comment. Then, what is
the proper/expec
019, at 12:57 PM, Joseph Lorenzini wrote:
>
> Hi all,
>
> I have question about the managed schema functionality. According to the
> docs, "All changes to a collection’s schema require reindexing". This would
> imply that if you use a managed schema and you use the sche
Hi all,
I have question about the managed schema functionality. According to the
docs, "All changes to a collection’s schema require reindexing". This would
imply that if you use a managed schema and you use the schema API to update
the schema, then doing a full re-index is necessary
t;
> Is there no way to use a custom schema to create a core from the command
> line? Will I always have to either hand edit the managed-schema, or use the
> API?
>
> Thanks,
>
> Rhys
e/7_0/coreadmin-api.html#coreadmin-create
says that schema is a valid parameter, and it explains how to use it.
But when I use the command create, I get an error.
Is there no way to use a custom schema to create a core from the command
line? Will I always have to either hand edit the managed-sch
> managed-schemas to use when creating cores.
>
> /tmp/solr_schema/CORENAME/managed-schema
>
> Based on this page:
> https://lucene.apache.org/solr/guide/7_0/coreadmin-api.html#coreadmin-create
> , I am running the following command:
>
> sudo -u solr /opt/solr/bin/so
I have created a tmp directory where I want to have reside custom
managed-schemas to use when creating cores.
/tmp/solr_schema/CORENAME/managed-schema
Based on this page:
https://lucene.apache.org/solr/guide/7_0/coreadmin-api.html#coreadmin-create
, I am running the following command:
sudo -u
Environment: Solr 7.4
I use mutable managed schema. I need a way for getting notification when a new
field is added into schema.
First, I try to extend "org.apache.solr.schema.ManagedIndexSchema".
Unfortunately, it is defined as final class, so that I am not able to extend it.
T
e treated as template to copy.
>
> That is more of a trick than production approach though.
>
> Regards,
>Alex
>
>
>
> On Wed, Jul 25, 2018, 1:04 PM Chuming Chen, wrote:
>
>> Hi All,
>>
>> From Solr Admin interface, I have created a collection
On 7/25/2018 11:04 AM, Chuming Chen wrote:
> From Solr Admin interface, I have created a collection and added field
> definitions. I can get its managed-schema from the Admin interface.
>
> Can I use this managed-schema to create a new collection? If yes, how?
What Solr version?
T
Chuming Chen, wrote:
> Hi All,
>
> From Solr Admin interface, I have created a collection and added field
> definitions. I can get its managed-schema from the Admin interface.
>
> Can I use this managed-schema to create a new collection? If yes, how?
>
> Thanks,
>
> Chuming
>
>
managed-schema
Hi All,
>From Solr Admin interface, I have created a collection and added field
>definitions. I can get its managed-schema from the Admin interface.
Can I use this managed-schema to create a new collection? How?
Thanks,
Chuming
Hi All,
From Solr Admin interface, I have created a collection and added field
definitions. I can get its managed-schema from the Admin interface.
Can I use this managed-schema to create a new collection? How?
Thanks,
Chuming
Hi All,
From Solr Admin interface, I have created a collection and added field
definitions. I can get its managed-schema from the Admin interface.
Can I use this managed-schema to create a new collection? If yes, how?
Thanks,
Chuming
"And that managed-schema will reorder the entries and delete the comments
on first API modification." - This is something very irritating when
comparing files with the default version of Solr to see what has changed.
When upgrading schemas/configs for new version of Solr, such aut
onfig. Especially a large,
> complex deployment. But most Solr instances I see are not in the giant,
> complex to config variety and the config file approach is simplest for most
> teams.
>
> At least that's my 2 cents :)
> -Doug
>
>
> On Tue, Jun 19, 2018 at 11:58 AM
Elastic allows the mappings to be set all at once, either in the template or as
index settings. That is an important feature because it allows the field
definitions to be source code artifacts, which can be deployed very easily by
an automatic script.
Solr's Managed Schema API allows mul
fit to the managed config. Especially a large,
complex deployment. But most Solr instances I see are not in the giant,
complex to config variety and the config file approach is simplest for most
teams.
At least that's my 2 cents :)
-Doug
On Tue, Jun 19, 2018 at 11:58 AM Alexandre Rafalovitch
wro
And that managed-schema will reorder the entries and delete the comments on
first API modification.
Regards,
Alex
On Tue, Jun 19, 2018, 11:47 AM Shawn Heisey, wrote:
> On 6/17/2018 6:48 PM, S G wrote:
> > I only wanted to know if schema.xml offer anything that managed-schema
>
On 6/17/2018 6:48 PM, S G wrote:
> I only wanted to know if schema.xml offer anything that managed-schema does
> not.
The only difference between the two is that there is a different
filename and the managed version can be modified by API calls. The
schema format and what you can do withi
I think my query got misinterpreted.
I only wanted to know if schema.xml offer anything that managed-schema does
not.
Best,
SG
On Sat, Jun 16, 2018 at 6:45 PM Erick Erickson
wrote:
> Currently, there are no restrictions on hand-editing config files,
> mutable or not.
>
> The rub
shed, and later
> might be confirmed to still be the same 'unmutable' state. Hand editing
> would violate that contract.
>
> One might also imagine a future where 'managed-schema' isn't a config file,
> and is just an API you use to configure a Solr. In this
me 'unmutable' state. Hand editing
would violate that contract.
One might also imagine a future where 'managed-schema' isn't a config file,
and is just an API you use to configure a Solr. In this case 'mutable'
doesn't imply anything about files, just the state o
Hi,
As per
https://lucene.apache.org/solr/guide/7_2/schema-factory-definition-in-solrconfig.html#SchemaFactoryDefinitioninSolrConfig-Classicschema.xml,
the only difference between schema.xml and managed-schema is that one
accepts schema-changes through an API while the other one does not
https://issues.apache.org/jira/secure/Dashboard.jspa
You have to create a login, but then you can raise a Solr JIRA.
Please put in all the detail you can to help someone reproduce.
One more thing to try: Rename your managed-schema to something like
testschema.xml, and change your solrconfig as
Thanks Erick,
I have made changes on the Master/indexing that are replicated to the Slave and
the managed-schema does not come over. Sounds like a JIRA entry may be in
order. How do I go about doing that? I am not using ConfigSets as each Core has
its own unique Schema.
Regards,
Kelly
On a quick glance at the code, I don't see anything requiring an xml
extension for the managed schema. I suppose it's possible that the
hyphen is messing things up.
You should see a message like:
"Adding config files to list: " .. on replication if you turn on
debug-leve
Hello all,
I need to replicate the managed-schema in my Solr 6.6.2 Master/Slave
environment and have added the necessary replication handlers. However, as the
managed-schema does not have a file extension it doesn't seem to get picked
up/replicated:
schema.xml,managed-schema,stopwords.tx
ern, I'm letting Solr have its default. I still make
manual edits, I just do it to a managed-schema file instead of schema.xml.
I have never used the Schema API that becomes possible with the managed
schema. But even though I'm not using that functionality, I let Solr
have its de
solr
then automatically reverts to the managed-schema.. which also works.
This is all part of a quick-start tutorial...
My idea was, in order to avoid confusion, which has been arising when
people start to modify schema.xml,... is to set Solr back into
"schema-mode" by having the user issue a com
On 2/23/2018 6:23 AM, BlackIce wrote:
I'm reworking some documentation for the Nutch project, and for the sake of
correctness and completness could someone tell me at which version did Solr
switch over to the "managed-Schema" by default?
It was version 5.5.
In the versions b
hi,
I'm reworking some documentation for the Nutch project, and for the sake of
correctness and completness could someone tell me at which version did Solr
switch over to the "managed-Schema" by default?
Thank you very much!
RRK
What if you include the core name as part of the direct path?
In my practice, managed-schema file is stored under ~/solr/coreName, so it
is core specific and will never be shared with other cores.
Wendy
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Hi Solr experts:
Question: how can I prevent multiple concurrent requests adding the same
duplicated copyfield into managed schema? (Note: I am using Solr 6.6.2)
User case: For a new field named srcField, I need to create another field named
destField, and a new copyField with srcField as
Hi,
I think it would be good to move the lang-configurations from
managed-schema to its own xml file as discussed in
https://issues.apache.org/jira/browse/SOLR-11948
What do other people think?
Thanks
SG
Actually, I think Solr does rearrange everything to its liking
(alphabetical?) when it rewrites managed-schema. So, if the
definitions are added via API, the order will be deterministic.
That's what I believe though, I can't remember testing it exhaustively
with physically rearra
Thanks!
On 12/20/2017 11:37 AM, Erick Erickson wrote:
The schema is not order dependent, I freely mix-n-match the fieldType,
copyField and field definitions for instance.
On Wed, Dec 20, 2017 at 8:29 AM, Michael Joyner wrote:
Hey all,
I'm wanting to update our managed-schemas to include t
The schema is not order dependent, I freely mix-n-match the fieldType,
copyField and field definitions for instance.
On Wed, Dec 20, 2017 at 8:29 AM, Michael Joyner wrote:
> Hey all,
>
> I'm wanting to update our managed-schemas to include the latest options
> available in the 6.6.2 branch. (po
Hey all,
I'm wanting to update our managed-schemas to include the latest options
available in the 6.6.2 branch. (point types for one)
I would like to be able to sort them and diff them (production vs dist
supplied) to create a simple patch that can be reviewed, edited if
necessary, and then
>multivalued
>field: post_title
>
>I can need specific field as multivalue, it's a bug in my app
>
>what I change in solrconfig.xml please?
>
>Thanks
>
>
>
>--
>View this message in context:
>http://lucene.472066.n3.nabble.com/Managed-Schema-multiValued-Predict
66.n3.nabble.com/Managed-Schema-multiValued-Predict-Problem-tp4324634p4331936.html
Sent from the Solr - User mailing list archive at Nabble.com.
On 3/20/2017 9:22 AM, Issei Nishigata wrote:
> Is my understanding correct that managed-schema is not limited that it
> can be modified only via Schema API, but that we usually modify it via
> Schema API, and we also can modify what Schema API can't do by
> hand-editing? N
Thank you for these information.
but I am still confusing about specification of managed-schema.
I recognize that I cannot modify "unique id" or "Similarity" by Schema API
now.
* https://issues.apache.org/jira/browse/SOLR-7242
Isn't there any other way than hand-editin
Hey Jay!
All I can say is "good luck with that". I do know Morphlines uses
EmbeddedSolrServer to do its work. So I don't really see a good way to
pluck just what you'd need for schemaless.
The MapReduceIndexerTool is carried right along with Solr though. IIRC
the Morphlines stuff is mostly the ET
I've got a very difficult project to tackle. I've been tasked with using
schemaless mode to index json files that we receive. The structure of the
json files will always be very different as we're receiving files from
different customers totally unrelated to one another. We are attempting to
build
You are right, I mean schemaless mode. I saw that it's your answer ;) I've
edited solrconfig.xml and fixed it. Thanks!
On Mon, Mar 13, 2017 at 5:46 PM, Alexandre Rafalovitch
wrote:
> There is managed schema, which means it is editable via API, and there
> is 'schemaless&#x
There is managed schema, which means it is editable via API, and there
is 'schemaless' mode that uses that to auto-define the field based on
the first occurance.
'schemaless' mode does not know if the field will be multi-valued the
first time it sees content for that field
he on multivalued field and don't want it to be
> multivalued. When I check managed-schema I see that:
>
>positionIncrementGap="0" docValues="true" precisionStep="0"/>
>positionIncrementGap="0" docValues="true" multiVa
Field
and
Multivalued.
I want to use FieldCache on multivalued field and don't want it to be
multivalued. When I check managed-schema I see that:
So, it seems that it's predicted as longs instead of long.
What is the reason behind that?
Kind Regards,
Furkan KAMACI
I suggest we make additional comments on SOLR-10241. I created it as a
result of this discussion and anyone who takes it on would benefit
from the comments being made there.
Anyone can make comments there, there's no special karma required
although you do have to create a login. From the interest
Actually, the main cross-references are from the solrconfig.xml, and
primarily from the Update Request Handler chain that creates the
"schemaless" effect. Then, I think you also have highlighters, etc.
I did that full analysis as a presentation at the last Solr
Revolution:
https://www.slideshare.
On 3/7/2017 1:32 PM, Phil Scadden wrote:
I would have to say the "basic-config" seems distinctly more than
basic. It is still a huge file. I thought perhaps I could delete every
unused field type, but worried there were some "system" dependencies.
This is definitely true. Solr example configs
t; In the reference guide, in the chapter named "The Well Configured Solr
> Instance", it says (I'm copying+pasting from the PDF version) :
>
> Switching from Managed Schema to Manually Edited schema.xml
>> If you have started Solr with managed schema enabled and you would
In the reference guide, in the chapter named "The Well Configured Solr
Instance", it says (I'm copying+pasting from the PDF version) :
Switching from Managed Schema to Manually Edited schema.xml
> If you have started Solr with managed schema enabled and you would like to
&g
See SOLR-10241 I just opened for discussion. My first impulse (well
actually second) is to _not_ encourage anyone to hand-edit managed
schema, and especially not put that in the ref guide.
But perhaps put the classic schema factory in a comment in
basic_configs and direct people there (and maybe
I would second that guide could be clearer on that. I read and reread several
times trying to get my head around the schema.xml/managed-schema bit. I came
away from first cursory reading with the idea that managed-schema was mostly
for schema-less mode and only after some stuff ups and puzzling
On 7 March 2017 at 15:02, OTH wrote:
> Specifically, that 'managed-schema' could indeed be modified by hand, or
> even that what the HTTP API is doing is actually modifying this file.
Thank you for the specific feedback. That is something we should fold
into the Guide as you are
ecifically, that 'managed-schema' could indeed be modified by hand, or
even that what the HTTP API is doing is actually modifying this file.
When I was first checking out Solr, I saw this section and remembered
thinking how verbose it was to make changes this way, because I saw on some
web
uence/display/solr/Schema+API
Regards,
Alex.
http://www.solr-start.com/ - Resources for Solr users, new and experienced
On 7 March 2017 at 11:41, OTH wrote:
> Hello
>
> I'm sure this has been asked many times but I'm having some confusion here.
>
> I understand that
; I understand that managed-schema is not supposed to be edited by hand but
> > only via the "API". All I understand about this "API" however, is that
> it
> > may be referring to the "Schema" page in the Solr browser-based Admin.
> >
> &g
:00 OTH :
> Hello
>
> I'm sure this has been asked many times but I'm having some confusion here.
>
> I understand that managed-schema is not supposed to be edited by hand but
> only via the "API". All I understand about this "API" however, is that i
On 3/7/2017 9:41 AM, OTH wrote:
> I understand that managed-schema is not supposed to be edited by hand but
> only via the "API". All I understand about this "API" however, is that it
> may be referring to the "Schema" page in the Solr browser-based Admin.
Hello
I'm sure this has been asked many times but I'm having some confusion here.
I understand that managed-schema is not supposed to be edited by hand but
only via the "API". All I understand about this "API" however, is that it
may be referring to the "Sch
2/27/2017 4:46 AM, Issei Nishigata wrote:
> Thank you for your reply. If I was to say which one, I'd maybe be
> talking about the concept for Solr. I understand we should use
> "ClassicSchemaFactory" when we want to hand-edit, but why are there
> two files, schema.xml a
emaFactory" when we want to
> hand-edit, but why are there two files, schema.xml and managed-schema, in
> spite that we can hand-edit managed-schema? If we can modify the schema.xml
> through Schema API, I think we won't need the managed-schema, but is there
> any reason why t
Thank you for your reply.
If I was to say which one, I'd maybe be talking about the concept for Solr.
I understand we should use "ClassicSchemaFactory" when we want to
hand-edit, but why are there two files, schema.xml and managed-schema, in
spite that we can hand-edit managed-sc
This is the sequence that gets you in trouble:
> start solr
> hand edit the schema _without_ reloading your collection or restarting all
> your Solr instances.
> use the managed-schema API to make modifications.
In this scenario your hand-edits can be lost since the in-memory ve
PI?
https://cwiki.apache.org/confluence/display/solr/Major+Changes+from+Solr+5+to+Solr+6
In the answer to the past question, it seemed okay.
http://lucene.472066.n3.nabble.com/Solr-6-managed-schema-amp-version-control-td4289243.html
I was worried because managed-schema said "" whe
Regards,
~Sri
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Monday, February 06, 2017 10:21 PM
To: solr-user
Subject: Re: Switching from Managed Schema to Manually Edited schema.xml --IS
NOT WORKING
You did not answer whether you uploaded your configs to
d you mind sharing config files for indexing text document?
>
> Regards,
> ~Sri
>
> -Original Message-
> From: Erick Erickson [mailto:erickerick...@gmail.com]
> Sent: Monday, February 06, 2017 12:22 AM
> To: solr-user
> Subject: Re: Switching from Managed Sche
06, 2017 12:22 AM
To: solr-user
Subject: Re: Switching from Managed Schema to Manually Edited schema.xml --IS
NOT WORKING
This is still using the managed schema specifically the data_driven_configs
schema as evidenced by the add-unknown-field-to-the-schema part of the URL.
It looks like you&#x
This is still using the managed schema specifically the
data_driven_configs schema as evidenced by the
add-unknown-field-to-the-schema part of the URL.
It looks like you're not _really_ removing the managed schema
definitions from your solrconfig.xml. You must
1> change solrconfig.xml
2&
Hi ,
I am indexing a Text document and followed the steps defined in below URL to
create the schema.xml
https://cwiki.apache.org/confluence/display/solr/Schema+Factory+Definition+in+SolrConfig#SchemaFactoryDefinitioninSolrConfig-SwitchingfromManagedSchematoManuallyEditedschema.xml
After making a
;
>>> Newsletter and resources for Solr beginners and intermediates:
>>> http://www.solr-start.com/
>>>
>>>
>>> On 10 August 2016 at 18:28, Pierre Caserta wrote:
>>>> It did not work,
>>>> I tried many things and ended u
ny things and ended up trying this:
>>>
>>> >> class="solr.DataImportHandler">
>>>
>>>solr-data-config.xml
>>>
>>>
>>>
>>>
>>> add-unknown-fields-to-the-schema
>>
gt;
>>
>>solr-data-config.xml
>>
>>
>>
>>
>> add-unknown-fields-to-the-schema
>>
>>
>>
>> Regards,
>> Pierre
>>
>>> On 10 Aug 2016, at 18:08, Alexandre Rafalovitch wrote:
>&
vitch wrote:
>>
>> Your initParams section does not apply to /dataimport handler as
>> defined. Try modifying it to say:
>> path="/update/**,/dataimport"
>>
>> Hopefully, that's all that takes.
>>
>> Managed schema is enabled by default
apply to /dataimport handler as
> defined. Try modifying it to say:
> path="/update/**,/dataimport"
>
> Hopefully, that's all that takes.
>
> Managed schema is enabled by default, but schemaless mode is the next
> layer on top. With managed schema, you can use the API
Your initParams section does not apply to /dataimport handler as
defined. Try modifying it to say:
path="/update/**,/dataimport"
Hopefully, that's all that takes.
Managed schema is enabled by default, but schemaless mode is the next
layer on top. With managed schema, you can use
config but I get the same result.
true
managed-schema
How can I update my schemaless URP chain and add the parameter to call it to
DIH?
> On 10 Aug 2016, at 17:43, Alexandre Rafalovitch wrote:
>
> Do you have the actual fields defined? If not, then I am guessing that
&
2, Pierre Caserta wrote:
> Hi,
> It seems that using the DataImportHandler with a XPathEntityProcessor config
> with a managed-schema setup, only import the id and version field.
>
> data-config.xml
>
>
>
>
> processor="XPathEntityPro
Hi,It seems that using the DataImportHandler with a XPathEntityProcessor config with a managed-schema setup, only import the id and version field.data-config.xml processor="XPathEntityProcessor" stream="true" forEach="/p
ading arbitrary XML to
a website) so had to pull it all out.
The managed schema API is a was to have front-ends that
change the schema and config.
Best,
Erick
On Fri, Jul 29, 2016 at 7:19 AM, Shawn Heisey wrote:
> On 7/27/2016 12:37 PM, Rachid Bouacheria wrote:
>> I know that there still is
On 7/27/2016 12:37 PM, Rachid Bouacheria wrote:
> I know that there still is the option to use schema.xml by using the
> ClassicIndexSchemaFactory but I am curious to hear from y'all that use
> managed schema how you are doing it and if there are any downside,
> gotchas, or if
back.
> > >
> > > On Wed, Jul 27, 2016 at 2:24 PM, Erick Erickson <
> erickerick...@gmail.com
> > >
> > > wrote:
> > >
> > > > Using classic schema is perfectly acceptable/reasonable, you can
> > > > continue to do so freely
ontinue to do so freely (you'll have to change to
> > > ClassicSchemaFactory though).
> > >
> > > Also, you can freely edit managed-schema just as you did schema.xml.
> > > The "trick" here is that you have to take some care _not_ to issue
> >
our feed back.
>
> On Wed, Jul 27, 2016 at 2:24 PM, Erick Erickson
> wrote:
>
> > Using classic schema is perfectly acceptable/reasonable, you can
> > continue to do so freely (you'll have to change to
> > ClassicSchemaFactory though).
> >
> > Also, y
you can freely edit managed-schema just as you did schema.xml.
> The "trick" here is that you have to take some care _not_ to issue
> commands that modify the schema or the in-memory version will
> overwrite the one in ZK. Otherwise, though, you can freely use
> managed-schema
Using classic schema is perfectly acceptable/reasonable, you can
continue to do so freely (you'll have to change to
ClassicSchemaFactory though).
Also, you can freely edit managed-schema just as you did schema.xml.
The "trick" here is that you have to take some care _not_ to issu
Hi All,
I am upgrading from solr 4 to 6.
In solr 4 I have a schema.xml that is under version control.
But solr 6 has the notion of a managed schema that could be modified via a
solr api call.
This seems great and flexible, but my assumption is that in this case
zookeeper becomes the authoritative
ow.com/questions/24551835/available-gui-for-zookeeper
>> I used the Eclipse plugin before and while it is a bit clunky it gets the
>> job done.
>>
>>
>> Alexandre Drouin
>>
>>
>> -Original Message-
>> From: John Bickerstaff [mailto:j...@johnbickerstaff.com
ets the job
done.
Alexandre Drouin
-Original Message-
From: John Bickerstaff [mailto:j...@johnbickerstaff.com]
Sent: July 26, 2016 4:21 PM
To: solr-user@lucene.apache.org
Subject: Re: Can't load schema managed-schema: unknown field 'id'
Importance: High
@Michael - somewher
@John
I am using a managed schema with zookeeper/solrcloud.
On 07/26/2016 04:21 PM, John Bickerstaff wrote:
@Michael - somewhere there should be a "conf" directory for your SOLR
instance. For my Dev efforts, I moved it to a different directory and I
forget where it was, originally
ok...
I downloaded the config for both of my collections and the downloaded
managed-schema file shows "id" as defined? But the online view in the UI
shows it as not defined?
I've tried re-upping the config and nothing changes.
-Mike
On 07/26/2016 04:11 PM, John Bi
...@johnbickerstaff.com]
Sent: July 26, 2016 4:21 PM
To: solr-user@lucene.apache.org
Subject: Re: Can't load schema managed-schema: unknown field 'id'
Importance: High
@Michael - somewhere there should be a "conf" directory for your SOLR instance.
For my Dev efforts, I moved it
r on in the file...
>
>
> id
>
>
> On Tue, Jul 26, 2016 at 2:17 PM, John Bickerstaff <
> j...@johnbickerstaff.com> wrote:
>
>> I don't see a managed schema file. As far as I understand it, id is set
>> as a "uniqueKey" in the schema.xml f
and further on in the file...
<
uniqueKey>id
On Tue, Jul 26, 2016 at 2:17 PM, John Bickerstaff
wrote:
> I don't see a managed schema file. As far as I understand it, id is set
> as a "uniqueKey" in the schema.xml file...
>
> On Tue, Jul 26, 2016 at
1 - 100 of 160 matches
Mail list logo
