Hi Shaw,
Thank you for your response.
I can see the default value set to 1.0
version = schemaConf.getFloat(expression, 1.0f)
I can't see where an outside limit value is raised to the minimum (1.0) or
lowered to the maximum (1.6).
Regards.
Dominique
Le dim. 6 sept. 2020 à 00:25, Shawn Heisey
On 9/5/2020 3:30 AM, Dominique Bejean wrote:
Hi, I often see a bad usage of the version attribute in shema.xml. For
instance The version attribute is to
specify the schema syntax and semantics version to be used by Solr.
The current value is 1.6 It is clearly specified in schema.xml
comments
Hi Erick,
Thanks for the tip Admin>>UI>>(core)>>analysis, I will investigate this
afternoon.
Regards,
Bruno
-Message d'origine-
De : Erick Erickson [mailto:erickerick...@gmail.com]
Envoyé : vendredi 11 janvier 2019 17:18
À : solr-user
Objet : Re: Schem
apache.org
Objet : Re: Schema.xml, copyField, Slash, ignoreCase ?
Hi Bruno,
ignoreCase: Looks like you already have achieved this?
auto truncation: This is caused by inclusion of PorterStemFilterFactory in your
"text_en" field type. If you don't want its effects (i.e. treating dif
Hi Bruno,
ignoreCase: Looks like you already have achieved this?
auto truncation: This is caused by inclusion of PorterStemFilterFactory in your
"text_en" field type. If you don't want its effects (i.e. treating different
forms of the same word interchangeably), remove the filter.
process sla
The admin UI>>(select a core)>>analysis page is your friend here. It'll
show you exactly what each filter in your analysis chain does and from
there you'll need to mix and match filters, your tokenizer and the like
to support the use-cases you need.
My guess is that the field type you're using con
Seems odd to me as well. I suspect you can work around
this by either setting catenateall="0" or perserveOriginal="0"
Best,
Erick
On Fri, Oct 9, 2015 at 7:50 AM, Vincenzo D'Amore wrote:
> Hi,
>
> I have this fieldType configuration:
>
> positionIncrementGap="100">
>
>
> replacement=" " />
>
... 27 more
> Caused by: org.xml.sax.SAXParseException; systemId: solrres:/schema.xml;
> lineNumber: 3; columnNumber: 84; Error attempting to parse XML file
> (href='schema-common.xml').
> at org.apache.solr.core.Config.(Config.java:145)
> ... 29 more
>
> -Ursprüng
Hi Clemens,
I think the problem is the structure of the composite schema - you’ll end up
with:
<- your other schema file
<- the included schema-common.xml
tags from your schema-common.xml. You won’t be able to use
it alone in that case, but if you need to do that, you could j
On 3/18/2015 8:45 AM, Pedro Figueiredo wrote:
> Where can I find the xsd file for the schema.xml file?
As Erick said, current XSD files do not exist.
There are some (now probably outdated) XSD files in a patch on this issue:
https://issues.apache.org/jira/browse/SOLR-1758
Thanks,
Shawn
:( ok, thank you.
Pedro Figueiredo
Senior Engineer
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: 18 March 2015 15:28
To: solr-user@lucene.apache.org
Subject: Re: schema.xml xsd file
There isn't one. The question has ben bandied back and forth se
There isn't one. The question has ben bandied back and forth several times,
but
the reaction is that an XSD would be more trouble than it's worth,
especially as
it would have to handle any customizations that anyone wanted to throw at,
say,
custom field types.
Best,
Erick
On Wed, Mar 18, 2015 at
Solr does not index arbitrary XML, it only indexes XML in a very
specific format.
You could write some kind of SolrJ program that parsed your XML
docs and constructed the appropriate SolrInputDocuments.
You could use DIH with some of the XML/XSL transformations,
but be aware that the XSLT bits do
On Oct 23, 2011, at 20:23 , Fred Zimmerman wrote:
> So, basically, yes, it is a real problem and there is no designed solution?
Hmmm problem? Not terribly so, is it?
Certainly I'm more for a de-XMLification of configuration myself though. And
we probably should bake-in all the basic fi
So, basically, yes, it is a real problem and there is no designed solution?
e.g. optional sub-schema files that can be turned off and on?
On Sun, Oct 23, 2011 at 6:38 PM, Erik Hatcher wrote:
>
> On Oct 23, 2011, at 19:34 , Fred Zimmerman wrote:
> > it seems from my limited experience thus far th
On Oct 23, 2011, at 19:34 , Fred Zimmerman wrote:
> it seems from my limited experience thus far that as new data types are
> added, schema.xml will tend to become bloated with many different field and
> fieldtype definitions. Is this a problem in real life, and if so, what
> strategies are used
I always run
http://localhost:8983/solr/admin/cores?action=RELOAD&core=corename in the
browser when I wanna reload solr and see any changes in config xmls.
2011/7/27 François Schiettecatte
> I have not seen this mentioned anywhere, but I found a useful 'trick' to
> restart solr without having to
I have not seen this mentioned anywhere, but I found a useful 'trick' to
restart solr without having to restart tomcat. All you need to do is 'touch'
the solr.xml in the solr.home directory. It can take a few seconds but solr
will restart and reload any config.
Cheers
François
On Jul 27, 201
I believe you're fine with that. Don't need to reindex all solr database.
2011/7/27 Charles-Andre Martin
> Hi,
>
>
>
> We currently have a big index in production. We would like to add 2
> non-required fields to our schema.xml :
>
>
>
> required="false"/>
>
> required="false" multiValued="true
You should be fine - no need to re-index your data.
Adding and removing fields is generally safe to do without a re-index. Changing
a field (its type, analyzers, etc) requires more caution and generally does
require a re-index.
-Michael
On Tue, Jul 26, 2011 at 3:55 PM, Vignesh.v wrote:
> Dear Team,
>
> We tried changing the schema.xml to the user xml format but it
> shows error.Kindly give me a solution to carry out this process.
[...]
Sorry, what does that mean exactly? Please provide details
of what you tried, a
Thank you for your thorough response. Things make more sense now. Back to
the drawing board.
Alan.
On Tue, Feb 15, 2011 at 10:23 AM, Jonathan Rochkind wrote:
> You can't just send arbitrary XML to Solr for update, no. You need to send
> a Solr Update Request in XML. You can write software that
You can't just send arbitrary XML to Solr for update, no. You need to
send a Solr Update Request in XML. You can write software that
transforms that arbitrary XML to a Solr update request, for simple cases
it could even just be XSLT. There are also a variety of other mediator
pieces that come
Erick,
I think you put the finger on the problem. Our XML files (we get from our
suppliers) do *not* look like that.
That's what a typical file looks like
..
Obviously, nothing like
By the way, querying q=*:* retrieved "HTTP error 500 Null pointer
exception", which lea
Can we see a small sample of an xml file you're posting? Because it should
look something like
R16-500
more fields here.
Take a look at the Solr admin page after you've indexed data to see what's
actually in your index, I suspect what's in there isn't what you
expect.
Try q
Alan,
if you want to search the filename .. it has to be part of the
file-content itself. solr doesn't care about the filename itself, only
the content of the given file will be indexed.
HTH
Stefan
On Tue, Feb 15, 2011 at 1:15 AM, alan bonnemaison wrote:
> Hello!
>
> We receive from our supplie
Hi,
These two links helped me to solve the problem.
https://issues.apache.org/jira/browse/SOLR-1154
http://wiki.apache.org/solr/SolrReplication#enable.2BAC8-disable_master.2BAC8-slave_in_a_node
Thanks,
SRD
--
View this message in context:
http://lucene.472066.n3.nabble.com/schema-xml-in-other-
Chris,
Our solr conf folder is in read-only file system. But the data directory
(index) is not in read-only file system. As per our production environment
guidelines, the configuration files should be in read-only file system.
Thanks,
SRD
--
View this message in context:
http://lucene.472066.
: Thanks for your response. Our production environment is a read only file
: system. It is not allowing to modify or create new files under conf folder
: at runtime. So copy config through replication is not working for us.
if your entire production server is read only, where do you keep your
Erick,
Thanks for your response. Our production environment is a read only file
system. It is not allowing to modify or create new files under conf folder
at runtime. So copy config through replication is not working for us.
Thanks,
SRD
--
View this message in context:
http://lucene.472066.n3.
Why do you want to do this? What is the use case? There is already a
provision
for copying modified slave configurations from the master and renaming it in
the
process, would that suffice?
Best
Erick
On Thu, Jan 6, 2011 at 11:37 AM, Shanmugavel SRD
wrote:
>
> I want to place the schema.xml in a
Hi ,
There is no required fields except u specify any fields to required.U can
remove or add as many fields u want.
That is an example schema which shows how feilds are configured
--
View this message in context:
http://lucene.472066.n3.nabble.com/schema-xml-tp995696p995800.html
Sent from the S
It's seems like a copyField but is a group that I want ... and in your
version is not a group, I want the possibility to search in a group of field
using "AND" or "OR"
2010/5/7 Chris Hostetter
>
> :
> :
>
>
>
> ...
>
>
>
> group_name
>
>
>
>
> -Hoss
>
>
:
:
...
group_name
-Hoss
ntonello Mangone
> Sent: Fri 07-05-2010 15:26
> To: solr-user@lucene.apache.org;
> Subject: Re: schema.xml question
>
> For the moment I don't know how to do it, but I'll follow your suggestion
> :)
> Thank you very much ...
> ps. I'm just a novel
&g
I forgot, there is actually a proper wiki page on this subject:
http://wiki.apache.org/solr/SolrRequestHandler
-Original message-
From: Antonello Mangone
Sent: Fri 07-05-2010 15:26
To: solr-user@lucene.apache.org;
Subject: Re: schema.xml question
For the moment I don't kno
anation of
the subject.
[1]: http://wiki.apache.org/solr/SolrConfigXml
[2]:
http://svn.apache.org/repos/asf/lucene/dev/trunk/solr/example/solr/conf/solrconfig.xml
Cheers,
-Original message-
From: Antonello Mangone
Sent: Fri 07-05-2010 15:26
To: solr-user@lucene.apache.org;
S
For the moment I don't know how to do it, but I'll follow your suggestion :)
Thank you very much ...
ps. I'm just a novel
2010/5/7 Markus Jelsma
> You could write your own requestHandler in solrconfig.xml, it'll allow you
> to predefine parameters for your configured search components.
>
> -
You could write your own requestHandler in solrconfig.xml, it'll allow you to
predefine parameters for your configured search components.
-Original message-
From: Antonello Mangone
Sent: Fri 07-05-2010 15:17
To: solr-user@lucene.apache.org;
Subject: schema.xml question
Hello everyone,
: There is some work on SOLR-17 to track this. I put up a patch that's
: incomplete, based on the prior work done by Mike Baranczak and Hoss and
: others. I've been meaning to get back to it, but have been swamped.
Actually SOLR-17 tracks an XSD for the XML "response" format you get form
the X
Hey Guys,
There is some work on SOLR-17 to track this. I put up a patch that's
incomplete, based on the prior work done by Mike Baranczak and Hoss and others.
I've been meaning to get back to it, but have been swamped.
Contributions/updates welcome!
Cheers,
Chris
[1] http://issues.apache.org/
The same for me, IMO I think it should be nice to have that
Regards,
Andrea
Il 05/05/2010 11:58, Jon Poulton ha scritto:
Morning all,
I was wondering if anyone had written an XSD/DTD for schema.xml? A quick look
at the wiki (http://wiki.apache.org/solr/SchemaXml) suggests that this has yet
to
It doesn't really work with the schema.xml - I beat my head on it for
a few hours not long ago - maybe I sent an e-mail to this list about
it?
Yes, here:
http://www.lucidimagination.com/search/document/ba68aa6f2f7702c3/is_it_possible_to_use_xinclude_in_schema_xml
-Peter
On Wed, Jan 6, 2010 at
Otis Gospodnetic schrieb:
Attribute values for fields should be inherited from attribute values
of their field types.
Thanks, that answers my question pertaining to @indexed and @stored in
the "fieldtype" and "field" elements in "schema.xml".
Michael Ludwig
Attribute values for fields should be inherited from attribute values of their
field types.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
> From: Michael Ludwig
> To: solr-user@lucene.apache.org
> Sent: Monday, May 4, 2009 1:08:43 PM
> Subject
: > Are there any other compatibility issues between the would-be
: > Solr 1.3 and Solr 1.2?
:
: It shouldn't be a compatibility issue since both will be accepted.
Note that the example configs tend to represent the latest/greatest syntax
& features, but existing configs should generally contin
On Wed, Jul 9, 2008 at 7:13 PM, Teruhiko Kurosaka <[EMAIL PROTECTED]> wrote:
> I've noticed that schema.xml in the dev version of Solr spells
> what used to be fieldtype as fieldType with capital T.
>
> Are there any other compatibility issues between the would-be
> Solr 1.3 and Solr 1.2?
It shoul
PM
> To: solr-user@lucene.apache.org
> Subject: Re: schema.xml for CJK, German, French, etc.
>
>
> On Jul 2, 2008, at 9:16 PM, George Aroush wrote:
> > Has anyone created schema.xml for languages other then English?
>
> Indeed.
>
> > I like to
> > see a
On Jul 2, 2008, at 9:16 PM, George Aroush wrote:
Has anyone created schema.xml for languages other then English?
Indeed.
I like to
see a working example mainly for CJK, German and French. If you
have can
you share them?
TO get me started, I created the following for German:
On 14/08/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
>
> > 2 - Question about the structure of the injected xml file... does it
> > need to exactly match the data in solr? I know it makes sense that
> > we're only injecting the fields that solr needs and not excluding fields
> > that it needs...
1 - if we add fields / remove fields to be indexed, how will this affect
our current indexes. Will we need to completely recreate millions on
indexes (or is it indices)?
Depends what you are trying to do... if you are just adding or removing
fields, the index should be usable. For adding
51 matches
Mail list logo
