It worked! Thanks Mr. Rafalovitch. I just removed “type”: “query”.. keys from
the json, and used indexAnalyzer and queryAnalyzer in place of analyzer json
node.
Sent from Mail for Windows 10
From: Alexandre Rafalovitch
Sent: 03 March 2021 01:19
To: solr-user
Subject: Re: Schema API specifying
"analyzers": [{
> "type": "query",
> "tokenizer": {
> "class": "solr.StandardTokenizerFactory"
> },
> "filters": [
> {
> "class": "solr.LowerCaseFilterFactory"
> }
> ]
> },{
> "type": "index",
> "tokenizer": {
> "class": "solr.KeywordTokenizerFactory"
> },
> "filters": [
> {
> "class": "solr.LowerCaseFilterFactory"
> }
> ]
> }]
> }
> }
>
> "errorMessages":["Plugin init failure for [schema.xml]
> "msg":"error processing commands",...
>
> How can I specify different analyzers for query and index type when using
> schema api?
>
> Sent from Mail for Windows 10
>
{
"class": "solr.LowerCaseFilterFactory"
}
]
},{
"type": "index",
"tokenizer": {
"class": "solr.KeywordTokenizerFactory"
},
"filters": [
{
"class": "solr.LowerCaseFilterFactory"
}
]
}]
}
}
"errorMessages":["Plugin init failure for [schema.xml]
"msg":"error processing commands",...
How can I specify different analyzers for query and index type when using
schema api?
Sent from Mail for Windows 10
s my first time writing here. I
> >> hope I don't do anything wrong.
> >> I went to create the "bug" ticket and saw it would be a good idea to
> first
> >> talk to some of you via IRC (didn't work for me or I did something wrong
> >> after 20
dy,
>>
>> First of all, I wanted to say that this is my first time writing here. I
>> hope I don't do anything wrong.
>> I went to create the "bug" ticket and saw it would be a good idea to first
>> talk to some of you via IRC (didn't work for m
> after 20 years of not using it..)
>
> I'm currently using Solr 8.1.1 in production and I use the Schema API to
> create the necessary fields before starting to index my new data. (Reason,
> the managed-schema would be big for me to take care of and I decided to
> automate this pro
0 years of not using it..)
I'm currently using Solr 8.1.1 in production and I use the Schema API to
create the necessary fields before starting to index my new data. (Reason,
the managed-schema would be big for me to take care of and I decided to
automate this process by using the REST API).
I
On Thu, May 14, 2020 at 02:47:57PM -0600, Shawn Heisey wrote:
> On 5/14/2020 1:13 PM, Mark H. Wood wrote:
> > On Fri, Apr 17, 2020 at 10:11:40AM -0600, Shawn Heisey wrote:
> >> On 4/16/2020 10:07 AM, Mark H. Wood wrote:
> >>> I need to ask Solr 4.10 for the name of the unique key field of a
> >>> s
On 5/14/2020 1:13 PM, Mark H. Wood wrote:
On Fri, Apr 17, 2020 at 10:11:40AM -0600, Shawn Heisey wrote:
On 4/16/2020 10:07 AM, Mark H. Wood wrote:
I need to ask Solr 4.10 for the name of the unique key field of a
schema. So far, no matter what I've done, Solr is returning a 404.
The Luke Req
On Thu, May 14, 2020 at 03:13:07PM -0400, Mark H. Wood wrote:
> Anyway, I'll be reading up on how to upgrade to 5. (Hopefully not
> farther, just yet -- changes between, I think, 5 and 6 mean I'd have
> to spend a week reloading 10 years worth of data. For now I don't
> want to go any farther tha
:
> >
> >curl 'https://toolshed.wood.net:8443/isw6_3/solr/statistics/schema'
> >
> > We normally use the ClassicIndexSchemaFactory. I tried switching to
> > ManagedIndexSchemaFactory but it made no difference. Nothing is
> > logged for the fail
difference. Nothing is
logged for the failed requests.
From what I can see, the schema API handler was introduced in version
5.0. The SchemaHandler class exists in the released javadoc for the 5.0
version, but not the 4.10 version. You'll need a newer version of Solr.
Thanks,
Shawn
On Thu, Apr 16, 2020 at 02:00:06PM -0400, Erick Erickson wrote:
> Assuming isw6_3 is your collection name, you have
> “solr” and “isw6_3” reversed in the URL.
No. Solr's context is '/isw6_3/solr' and the core is 'statistics'.
> Should be something like:
> https://toolshed.wood.net:8443/solr/isw6
Assuming isw6_3 is your collection name, you have
“solr” and “isw6_3” reversed in the URL.
Should be something like:
https://toolshed.wood.net:8443/solr/isw6_3/schema/uniquekey
If that’s not the case you need to mention your collection. But in
either case your collection name comes after /solr/.
I need to ask Solr 4.10 for the name of the unique key field of a
schema. So far, no matter what I've done, Solr is returning a 404.
This works:
curl 'https://toolshed.wood.net:8443/isw6_3/solr/statistics/select'
This gets a 404:
curl 'https://toolshed.wood.net:8443/isw6_3/solr/statistics/
Hi - according to the documentation here:
https://lucene.apache.org/solr/guide/7_6/schema-api.html
The V2 API is located at api/cores/collection/schema
However the documentation here:
https://lucene.apache.org/solr/guide/7_6/v2-api.html
has it at api/c/collection/schema
I believe the later is
Hi Steve,
it is reasonable that schema api understand the commands only JSON. Great
that you'll update the ref guide. Thanks for taking care of it. Nice of you
:-)
Cheers,
Arturas
On Wed, Apr 18, 2018 at 3:27 PM, Steve Rowe wrote:
> Hi Arturas,
>
> The Schema API only understan
Hi Arturas,
The Schema API only understands commands in JSON. I looked through the ref
guide page, and I’m surprised that this isn’t stated directly; I’ll try to fix
that.
--
Steve
www.lucidworks.com
> On Apr 18, 2018, at 4:12 AM, Arturas Mazeika wrote:
>
> Hi solr-users,
&
Hi solr-users,
is it possible to modify the managed schema using schema api and submit the
commands in XML format? I am able to add a data type using:
curl -X POST -H 'Content-type:application/json' --data-binary '{
"add-field-type": {
"name":&quo
regularly pull it from ZK and put it in some VCS system
>> ;)
>
> Actually, I have the script that builds the schema in VCS, so it's
> roughly the same.
>
> As for the schema modifications... did I get those right?
>
> Thanks,
> - -chris
>
>> On Mon, Mar 12, 2018
>
> But as long as you don't mix-and-match hand-editing with using the
> schema API you can hand edit it freely. You're then in charge of
> pushing it to ZK and reloading your collections that use it
> yourself however.
No Zookeeper (yet), but I suspect I'll end up
raged":
> https://lucene.apache.org/solr/guide/6_6/schema-api.html.
>
> But as long as you don't mix-and-match hand-editing with using the
> schema API you can hand edit it freely. You're then in charge of
> pushing it to ZK and reloading your collections that use i
bq: which you aren't supposed to edit directly.
Well, kind of. Here's why it's "discouraged":
https://lucene.apache.org/solr/guide/6_6/schema-api.html.
But as long as you don't mix-and-match hand-editing with using the
schema API you can hand edit it freely. You&#
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I'd like to add a new synthesized field that uses a phonetic analyzer
such as Beider-Morse. I'm using Solr 7.2.
When I request the current schema via the schema API, I get a list of
existing fields, dynamic fields, and analyzer
just doing it iteratively through
> the API.
>
> Regards,
> André
>
>
> 2018-01-05 15:05 GMT+01:00 Shawn Heisey :
>
> > On 1/5/2018 6:51 AM, André Widhani wrote:
> >
> >> I know I can retrieve the entire schema using Schema API and I can also
> >> u
5 GMT+01:00 Shawn Heisey :
> On 1/5/2018 6:51 AM, André Widhani wrote:
>
>> I know I can retrieve the entire schema using Schema API and I can also
>> use
>> it to manipulate the schema by adding fields etc.
>>
>> I don't see any way to post an entire schema
On 1/5/2018 6:51 AM, André Widhani wrote:
I know I can retrieve the entire schema using Schema API and I can also use
it to manipulate the schema by adding fields etc.
I don't see any way to post an entire schema file back to the Schema API
though ... this is what most REST APIs offer
Hi,
I know I can retrieve the entire schema using Schema API and I can also use
it to manipulate the schema by adding fields etc.
I don't see any way to post an entire schema file back to the Schema API
though ... this is what most REST APIs offer: You retrieve an object,
modify it and send
Hi,
The schema api does not support XML requests, and there are currently no plans
I’m aware of to add support.
--
Steve
www.lucidworks.com
> On Nov 28, 2017, at 8:23 AM, startrekfan wrote:
>
> Hey
>
> Does the schema api supports xml requests? I tried to post a xml formatt
Hey
Does the schema api supports xml requests? I tried to post a xml formatted
"add-field" but got an parser exception. Is there no xml support? Is it
planned to add xml support within the next few months?
Thanks
as unique key (uniqueness is OK) and
do this kind of update.
Regards,Nabil.
De : Shawn Heisey
À : solr-user@lucene.apache.org
Envoyé le : Lundi 27 mars 2017 17h00
Objet : Re: Schema API: Modify Unique Key
On 3/27/2017 7:05 AM, nabil Kouici wrote:
> We're going to use Sol
On 3/27/2017 7:05 AM, nabil Kouici wrote:
> We're going to use Solr in our organization (under test) and we want
> to set the primary key through schema API, which is not allowed today.
> Is this function planned to be implemented in Solr? If yes, do you
> have any idea in which
27, 2017, at 9:05 AM, nabil Kouici wrote:
>
> Hi All,
>
>
>
> We're going to use Solr in our organization (under test) and we want to set
> the primary key through schema API, which is not allowed today. Is this
> function planned to be implemented in Solr? If
Hi All,
We're going to use Solr in our organization (under test) and we want to set the
primary key through schema API, which is not allowed today. Is this function
planned to be implemented in Solr? If yes, do you have any idea in which
version?
Regards,Nabil.
Looks like I ran into the same as was discussed here:
http://grokbase.com/t/lucene/solr-user/15c4nr1j48/solrcloud-1-server-1-configset-multiple-collections-multiple-schemas
Would be nice if that would be changed in the future as it would make
these setups much easier.
On 29/04/16 20:07, Hendrik H
Hi,
I have a Solr Cloud 6 setup with a managed schema. It seems like when I
create multiple collections from the same config set that they still
share the same schema. That was rather unexpected, as in the REST and
SolrJ API I do specify a collection when doing the schema change.
Looking into what
On 12/11/2015 8:02 AM, Yago Riveiro wrote:
> I uploaded a schema.xml manualy with the defaultoperator configuration and
> it's working.
>
> My problem is that my legacy application is huge and I can't go to all places
> to add the q.op parameter.
>
> The solrconfig.xml option should be an optio
t handlers works with POST http calls?
On Fri, Dec 11, 2015 at 2:26 PM, Shawn Heisey wrote:
> On 12/11/2015 4:23 AM, Yago Riveiro wrote:
>> How can I change the defaultoperator parameter through the schema API?
> The default operator and default field settings in the schema have been
On 12/11/2015 4:23 AM, Yago Riveiro wrote:
> How can I change the defaultoperator parameter through the schema API?
The default operator and default field settings in the schema have been
deprecated for quite some time, so I would imagine that you can't change
them with the schema API
Hi,
How can I change the defaultoperator parameter through the schema API?
Thanks.
-
Best regards
--
View this message in context:
http://lucene.472066.n3.nabble.com/Schema-API-change-the-defaultoperator-tp4244857.html
Sent from the Solr - User mailing list archive at Nabble.com.
eve
>
> > On May 6, 2015, at 6:44 PM, Steven White wrote:
> >
> > Hi Everyone,
> >
> > I am using the Schema API to add a new copy field per:
> >
> https://cwiki.apache.org/confluence/display/solr/Schema+API#SchemaAPI-AddaNewCopyFieldRule
> >
> >
> On May 6, 2015, at 8:25 PM, Yonik Seeley wrote:
>
> On Wed, May 6, 2015 at 8:10 PM, Steve Rowe wrote:
>> It’s by design that you can copyField the same source/dest multiple times -
>> according to Yonik (not sure where this was discussed), this capability has
>> been used in the past to eff
On Wed, May 6, 2015 at 8:10 PM, Steve Rowe wrote:
> It’s by design that you can copyField the same source/dest multiple times -
> according to Yonik (not sure where this was discussed), this capability has
> been used in the past to effectively boost terms in the source field.
Yep, used to be r
are
designed to fail if there are any existing dependencies, while the replace-*
commands will maintain the dependencies if they exist.
Steve
> On May 6, 2015, at 6:44 PM, Steven White wrote:
>
> Hi Everyone,
>
> I am using the Schema API to add a new copy fie
Hi Everyone,
I am using the Schema API to add a new copy field per:
https://cwiki.apache.org/confluence/display/solr/Schema+API#SchemaAPI-AddaNewCopyFieldRule
Unlike the other "Add" APIs, this one will not fail if you add an existing
copy field object. In fact, after when I call th
is means the response of "fieldtypes" includes "fields" and
> "dynamicfields" as syntactic-sugar to let me know of the relationship this
> field-type has or is there more to it?
It’s FYI: this is the full list of fields and dynamic fields that use the given
pes" includes "fields" and
"dynamicfields" as syntactic-sugar to let me know of the relationship this
field-type has or is there more to it?
The reason why I care about this question is because I'm using Solr's
Schema API (see: https://cwiki.apache.org/conflue
Wow - that's really cool! Thank you!
-Joe
On Wed, Sep 10, 2014 at 12:29 PM, Anshum Gupta
wrote:
> You don't need to bring down the shards/collections, instead here's what
> you can do:
> * Retain the filename ("managed_schema", if you didn't change the default
> resource name).
> * Edit the fi
You don't need to bring down the shards/collections, instead here's what
you can do:
* Retain the filename ("managed_schema", if you didn't change the default
resource name).
* Edit the file locally
* Upload it to replace the current zk file.
* Reload the collection(s).
* Reindex
Here's another th
Thank you - yes that was my question. I should have stated that it was for
SolrCloud and hence a managed schema. Could I bring down the shards, edit
the managed schema on zookeeper, fire the shards back up and re-index?
-Joe
On Wed, Sep 10, 2014 at 11:50 AM, Anshum Gupta
wrote:
> Hi Joseph,
>
Hi Joseph,
It isn't supported by an exiting REST API (if that was your question) but
you can always edit the schema manually (if it isn't managed), upload the
new schema and reload the collections (or cores in case of non-SolrCloud
mode).
Do remember that changing the field type might require you
In addition to adding new fields to the schema, is there a way to modify an
existing field? If I created a field called userID as a long, but decided
later that it should be a string?
Thank you!
-Joe
te:
>>
>>> Hello everybody,
>>>
>>> from reading the documentation it is not entirely clear what the
>>> synchronization behavior of Solr's schema API is. We are seeing some
>>> reliability issues in a multi-machine SolrCloud setup. Grante
ing the documentation it is not entirely clear what the
> > synchronization behavior of Solr's schema API is. We are seeing some
> > reliability issues in a multi-machine SolrCloud setup. Granted, being new
> > we might be doing something wrong, but at this point I am confused
it is not entirely clear what the
> synchronization behavior of Solr's schema API is. We are seeing some
> reliability issues in a multi-machine SolrCloud setup. Granted, being new
> we might be doing something wrong, but at this point I am confused as to
> what the expected behavior ou
Hello everybody,
from reading the documentation it is not entirely clear what the
synchronization behavior of Solr's schema API is. We are seeing some
reliability issues in a multi-machine SolrCloud setup. Granted, being new
we might be doing something wrong, but at this point I am confused
Thank you Chris,
Exactly as you suggested I was looking into related classes to that one.
Playing with :
@BeforeClass
> public static void init() throws Exception {
> final SortedMap extraServlets = new
> TreeMap();
> final ServletHolder solrRestApi = new ServletHolder("SolrRestApi",
>
EmbeddedSolrServer is really just for dealing with embedded SolrCore
objects. It doesn't have ay of the other HTTP related plumbing
assocaited with it -- which is why it can't be used for replication and/or
cloud features, let alone the RESTLet based endpoints.
if you want to write a test tha
Hi guys,
I'm struggling testing schemaAPI REST endpoints thourgh EmbeddedSolrServer.
Out of the box the Embedded Solr Server is not able to recognize the schema
request handler. So I was trying to follow an approach like this :
public static void init() throws Exception {
> final SortedMap ex
uery = new SolrQuery();
>>> if (dynamicFields)
>>> query.setRequestHandler(DYNAMIC_FIELDS_API);
>>> else
>>> query.setRequestHandler(DEFINED_FIELDS_API);
>>> query.setParam("showDefaults"
.setParam("showDefaults", true);
>>
>> QueryResponse response = solrConn.query(query)
>>
>> Then you've got to parse the response using NamedList etc.etc.
>>
>> -Original Message-
>> From: Alessandro Benedetti [mailto:benedetti.ale...@
etParam("showDefaults", true);
>
> QueryResponse response = solrConn.query(query)
>
> Then you've got to parse the response using NamedList etc.etc.
>
> -Original Message-
> From: Alessandro Benedetti [mailto:benedetti.ale...@gmail.com]
> Sen
've got to parse the response using NamedList etc.etc.
-Original Message-
From: Alessandro Benedetti [mailto:benedetti.ale...@gmail.com]
Sent: Tuesday, July 08, 2014 5:54 AM
To: solr-user@lucene.apache.org
Subject: [Solr Schema API] SolrJ Access
Hi guys,
wondering if there is any proper
Hi guys,
wondering if there is any proper way to access Schema API via Solrj.
Of course is possible to reach them in Java with a specific Http Request,
but in this way, using SolrCloud for example we become coupled to one
specific instance ( and we don't want) .
Code Ex
On 7/6/2013 4:27 PM, Steven Glass wrote:
Thanks for your response.
But it seems like there should be a way to issue the equivalent of
http://localhost:8983/solr/schema/version
which returns
{
"responseHeader":{
"status":0,
"QTime":4},
"version":1.5}
from the s
You _should_ be able to use an HttpSolrServer, set
the base URL and then go ahead and make the
request. Haven't done it myself, but the SolrJ
"support" for various Solr features often consists of
just convenience methods over the underlying HTTP,
saving you the necessity of, say, parsing the respon
Thanks for your response.
But it seems like there should be a way to issue the equivalent of
http://localhost:8983/solr/schema/version
which returns
{
"responseHeader":{
"status":0,
"QTime":4},
"version":1.5}
from the server. I know how to do it using HTTPGet in
Steven,
Some information can be gleaned from the "system" admin request handler:
http://localhost:8983/solr/admin/system
I am specifically looking at this:
example
Mind you, that is a manually-set value in the schema file. But just in case
you want to get crazy you can also call the "file" a
Does anyone have any idea how I can access the schema version info using SolrJ?
Thanks.
On Jul 3, 2013, at 4:16 PM, Steven Glass wrote:
> I'm using a Solr 4.3 server and accessing it from both a Java based desktop
> application using SolrJ and an Android based mobile application using my
> ho
I'm using a Solr 4.3 server and accessing it from both a Java based desktop
application using SolrJ and an Android based mobile application using my
home-grown REST adaptor. I'm trying to make sure that versions of the
application are synchronized with updates to the server (too often testers
70 matches
Mail list logo
