You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by jo <ja...@firmex.com> on 2011/10/03 22:22:52 UTC
schema changes changes 3.3 to 3.4?
Hi, I have the following issue on my test environment
when I do a query with the full word the reply no longer contains the
attr_meta
ex:
http://solr1:8983/solr/core_1/select/?q=stegosaurus
<arr name="attr_content_encoding">
<str>ISO-8859-1</str>
</arr>
<arr name="attr_content_language">
<str>en</str>
</arr>
but if I remove just one letter it shows the expected response
ex:
http://solr1:8983/solr/core_1/select/?q=stegosauru
<arr name="attr_content_encoding">
<str>ISO-8859-1</str>
</arr>
<arr name="attr_meta">
<str>stream_source_info</str>
<str>document</str>
<str>stream_content_type</str>
<str>text/plain</str>
<str>stream_size</str>
<str>81</str>
<str>Content-Encoding</str>
<str>ISO-8859-1</str>
<str>stream_name</str>
<str>filex123.txt</str>
<str>Content-Type</str>
<str>text/plain</str>
<str>resourceName</str>
<str>dinosaurs5.txt</str>
</arr>
For troubleshooting I replaced the schema.xml from 3.3 into 3.4 and it work
just fine, I can't find what changes on the schema would case this, any
clues?
--
View this message in context: http://lucene.472066.n3.nabble.com/schema-changes-changes-3-3-to-3-4-tp3391019p3391019.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: schema changes changes 3.3 to 3.4?
Posted by jo <ja...@firmex.com>.
Thanks, as a general rule a would totally agree, however the way we are
using solr we don't want to be attach to any particular schema, we just want
it to work with whatever the default is... but I will keep
your suggestion in mind in the future
thanks everyone.. you guys are always very helpful
On Mon, Oct 10, 2011 at 8:34 PM, Chris Hostetter-3 [via Lucene] <
ml-node+s472066n3411231h12@n3.nabble.com> wrote:
>
> : I figure it out.. thanks for pointing me in the right direction... so at
> the
> : end solr field type text was changed for text_general
>
> they key take away here seems to be that when you upgraded from Solr 3.3
> to Solr 3.4 you stoped using your old schema (which you copied from the
> 3.3 example), and started using the example schema from 3.4 -- which was
> different.
>
> This is not a good idea in general -- if you build an index with a
> specific set of configs, you should *not* change those configs just
> because you upgrade solr -- quite hte opposite, you should
> absolutely continue using your old configs when you upgrade the Solr
> application.
>
> There may be new recomendations in the new example configs that you want
> to read/consider, and by all means if you are building a *new* index
> consider using the new example configs as your starting point -- but under
> no circumstances should you blindly replace your existing (working)
> config files with the example from a new version of Solr just because you
> upgrade.
>
>
> -Hoss
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://lucene.472066.n3.nabble.com/schema-changes-changes-3-3-to-3-4-tp3391019p3411231.html
> To unsubscribe from schema changes changes 3.3 to 3.4?, click here<http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3391019&code=amFpcm8ub3J0aXpAZmlybWV4LmNvbXwzMzkxMDE5fDcwMjU4NDMxNQ==>.
>
>
--
View this message in context: http://lucene.472066.n3.nabble.com/schema-changes-changes-3-3-to-3-4-tp3391019p3412542.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: schema changes changes 3.3 to 3.4?
Posted by Chris Hostetter <ho...@fucit.org>.
: I figure it out.. thanks for pointing me in the right direction... so at the
: end solr field type text was changed for text_general
they key take away here seems to be that when you upgraded from Solr 3.3
to Solr 3.4 you stoped using your old schema (which you copied from the
3.3 example), and started using the example schema from 3.4 -- which was
different.
This is not a good idea in general -- if you build an index with a
specific set of configs, you should *not* change those configs just
because you upgrade solr -- quite hte opposite, you should
absolutely continue using your old configs when you upgrade the Solr
application.
There may be new recomendations in the new example configs that you want
to read/consider, and by all means if you are building a *new* index
consider using the new example configs as your starting point -- but under
no circumstances should you blindly replace your existing (working)
config files with the example from a new version of Solr just because you
upgrade.
-Hoss
Re: schema changes changes 3.3 to 3.4?
Posted by jo <ja...@firmex.com>.
I figure it out.. thanks for pointing me in the right direction... so at the
end solr field type text was changed for text_general
I was only missing this filters
<filter class="solr.KeywordMarkerFilterFactory"
protected="protwords.txt"/>
<filter class="solr.PorterStemFilterFactory"/>
On Wed, Oct 5, 2011 at 10:52 AM, jo [via Lucene] <
ml-node+s472066n3396737h98@n3.nabble.com> wrote:
> Okay I did use the analysis tool and it did make me notice a few things but
> more important what changed
>
> there is no longer a field type named "text" on the new schema, there is
> only "text_en" which is weird as text field is the default when doing a
> query..
> anyway, when I used the analysis tool and made the steamers and all match
> between the old schema and the new schema I get a result in the analysis
> tool but not in the query.
>
> I have to say that I have been using Solr with the default schema without
> any changes in the past, but since I upgraded to 3.4.0 I have this problem
> with the plurals not been displayed.
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://lucene.472066.n3.nabble.com/schema-changes-changes-3-3-to-3-4-tp3391019p3396737.html
> To unsubscribe from schema changes changes 3.3 to 3.4?, click here<http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3391019&code=amFpcm8ub3J0aXpAZmlybWV4LmNvbXwzMzkxMDE5fDcwMjU4NDMxNQ==>.
>
>
--
View this message in context: http://lucene.472066.n3.nabble.com/schema-changes-changes-3-3-to-3-4-tp3391019p3397078.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: schema changes changes 3.3 to 3.4?
Posted by jo <ja...@firmex.com>.
Okay I did use the analysis tool and it did make me notice a few things but
more important what changed
there is no longer a field type named "text" on the new schema, there is
only "text_en" which is weird as text field is the default when doing a
query..
anyway, when I used the analysis tool and made the steamers and all match
between the old schema and the new schema I get a result in the analysis
tool but not in the query.
I have to say that I have been using Solr with the default schema without
any changes in the past, but since I upgraded to 3.4.0 I have this problem
with the plurals not been displayed.
--
View this message in context: http://lucene.472066.n3.nabble.com/schema-changes-changes-3-3-to-3-4-tp3391019p3396737.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: schema changes changes 3.3 to 3.4?
Posted by jo <ja...@firmex.com>.
Interesting... I did not make changes on the default settings, but defenetely
will give that a shot.. thanks.... I will comment later if I found a
solution beside replacing the schema with the default one on 3.3
thanks
JO
--
View this message in context: http://lucene.472066.n3.nabble.com/schema-changes-changes-3-3-to-3-4-tp3391019p3395265.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: schema changes changes 3.3 to 3.4?
Posted by Erick Erickson <er...@gmail.com>.
It looks to me like you changed the analysis
chain for the field in question by removing
stemmers of some sort or other. The quickest
way to answer this kind of question is to get
familiar with the admin/analysis page (don't
forget to check the verbose checkboxes). Enter
the term in both the index and query boxes and
hit the button. It shows you exactly what parts
of the chain performed what actions.
So you index analysis chain probably removed
the plurals, but your query-side didn't. So I'm
guessing that not only didn't it show the
metadata, it didn't even find the document in
question.
But that's a guess at this point.
Best
Erick
On Mon, Oct 3, 2011 at 4:22 PM, jo <ja...@firmex.com> wrote:
> Hi, I have the following issue on my test environment
> when I do a query with the full word the reply no longer contains the
> attr_meta
> ex:
> http://solr1:8983/solr/core_1/select/?q=stegosaurus
>
> <arr name="attr_content_encoding">
> <str>ISO-8859-1</str>
> </arr>
> <arr name="attr_content_language">
> <str>en</str>
> </arr>
>
> but if I remove just one letter it shows the expected response
> ex:
> http://solr1:8983/solr/core_1/select/?q=stegosauru
>
> <arr name="attr_content_encoding">
> <str>ISO-8859-1</str>
> </arr>
> <arr name="attr_meta">
> <str>stream_source_info</str>
> <str>document</str>
> <str>stream_content_type</str>
> <str>text/plain</str>
> <str>stream_size</str>
> <str>81</str>
> <str>Content-Encoding</str>
> <str>ISO-8859-1</str>
> <str>stream_name</str>
> <str>filex123.txt</str>
> <str>Content-Type</str>
> <str>text/plain</str>
> <str>resourceName</str>
> <str>dinosaurs5.txt</str>
> </arr>
>
>
> For troubleshooting I replaced the schema.xml from 3.3 into 3.4 and it work
> just fine, I can't find what changes on the schema would case this, any
> clues?
>
> --
> View this message in context: http://lucene.472066.n3.nabble.com/schema-changes-changes-3-3-to-3-4-tp3391019p3391019.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>