highlighting, then open up a new tab with the Admin's query
> > interface. Same place on the left as the analyzer. Replace the "*:*" with
> > your search term (assuming you already indexed your document) and if
> > necessary you can put something in the FQ like
op left (in other words the term in the document you
>> are
>> > > indexing that you expect to get a hit on) and right input fields.
>> Select
>> > > the field that it is destined for (in your case that would be
>> 'content'),
>> > > th
any more suggestion where I could be
> >> missing something... please let me know.
> >> >
> >> >
> >> > Best regards,
> >> >
> >> > *Evert*
> >> >
> >> > 2015-12-16 15:30 GMT-02:00 Teague James <teag...@i
highlight. (PSST... Developers...
> It
> > > would be really cool if the highlight color were more visible or
> > > customizable... Thanks y'all) If it looks like you're getting hits, but
> > not
> > > getting highlighting, then open up a new tab with the Admin's q
Evert R. [mailto:evert.ra...@gmail.com]
Sent: Wednesday, December 16, 2015 1:46 PM
To: solr-user <solr-user@lucene.apache.org>
Subject: Re: Solr Basic Configuration - Highlight - Begginer
Hi Teague!
I configured the solrconf.xml and schema.xml exactly the way you did, only
substitut
December 15, 2015 6:25 AM
To: solr-user@lucene.apache.org
Subject: Solr Basic Configuration - Highlight - Begginer
Hi there!
It´s my first installation, not sure if here is the right channel...
Here is my steps:
1. Set up a basic install of solr 5.4.0
2. Create a new core through command line (b
Hi Erick,
I think you are right!
When I use the form 'features:accents' in my case 'content:nietava', it
show as if there was not matching words... but if I take the field off
having only the 'q=searchword' (q=nietava) it brings the pdf content file,
as below (in XML out type):
#partial snip:
>
>
>
> catenateAll="1" preserveOriginal="1" generateWordParts="0" />
> words="stopwords.txt" />
>
>
>
>
>
Ok, you're getting confused by all the options, an easy thing to do.
You're trying to do too many things at once without making sure
the basics work
1> Forget all about the f.content.hl stuff. That's there in case
you want to specify different parameters for different fields in the same
of course. The fq= is an example) :
> http://[URL/IP]/solr/[CORE-NAME]/select?fq=id:123456="[SEARCH-TERM];
>
> That will dump Solr's output to your browser where you can see exactly what
> is getting hit.
>
> Hope that helps! Let me know how it goes. Good luck.
>
> -Teague
>
ssuming you already indexed your document) and if
>> necessary you can put something in the FQ like "id:123456" to target a
>> specific record.
>> >
>> > Did you get a hit? If no, then it's not highlighting that's the issue.
>> If yes, then
not highlighting that's the issue.
> If yes, then try dumping this in your address bar (using your URL/IP,
> search term, and core name of course. The fq= is an example) :
> > http://[URL/IP]/solr/[CORE-NAME]/select?fq=id:123456="[SEARCH-TERM];
> >
> > That will dump S
Hi everyone!
I think I should not have posted my server name... never had that many
access attempts...
2015-12-16 9:03 GMT-02:00 Evert R. :
> Hello Erick,
>
> Thanks again for your time.
>
> Here is as far as I have gone:
>
> 1. I started a fresh install and did the
hl=f.content.hl.content (I guess) is definitely wrong. Some questions:
- First, sorry, the obvious question: are you sure the documents contain
the "nietava" term?
- Could you try to use q=content:nietaval?
- Could you paste the definition (field & fieldtype) of the content
field?
Hi Andrea,
Thanks for the reply!
I tried with the hl.fl parameter as well, using as below:
http://localhost:8983/solr/techproducts/select?q=nietava=id%2C+content=json=true=true;
hl.fl=f.content.hl.content%3D4=%3Cem%3E=%3C%2Fem%3E
with the parameter under the hl field in the solr ui:
1.
Hi Evert,
what is the configuration of the default request handler? Did you set the
hl.fl parameter?
Please check here [1] the parameters that the highlighting component
expects. Required parameters should be in the query string or declared
within the request handler which answers to your query.
Hello Erick,
Thanks again for your time.
Here is as far as I have gone:
1. I started a fresh install and did the following:
[evert@nix]$ bin/solr start -e techproducts
[evert@nix]$ curl '
http://localhost:8983/solr/techproducts/update/extract?literal.id=pdf1=true'
-F
Hi Andrea,
ok, let´s do it:
1. it does has the 'nietava' term, so it brings the only book (pdf file)
has this word, and all its content as my previous message to Erick, so the
content field is there.
2. using content:nietava it does not show any result as below:
{ "responseHeader": {
How are you trying to display the results? Highlighting is a bit of an
odd beast. Assuming it's correctly configured, the response packet
will have a separate highlight section, it's the application's
responsibility to present that pleasingly.
What _do_ you get bak in the response?
BTW, the mail
Hi Erick,
Thank you very much for the reply!!
I do get back the full text, autor, and a whole lots of stuff which doesn´t
really matter for my project.
So, what you are saying is that the solr gets me back the full content and
my application will fix the rest? Which means for me that all my
No, that's not what I meant. The highlight component adds a special
section to the return packet that will contain "snippets" of text with
highlights. You control how big those snippets are via various
parameters in the highlight component and they'll have the tags you
specify for highlighting.
Hi there!
It´s my first installation, not sure if here is the right channel...
Here is my steps:
1. Set up a basic install of solr 5.4.0
2. Create a new core through command line (bin/solr create -c test)
3. Post 2 files: 1 .docx and 2 .pdf (bin/post -c test /docs/test/)
4. Query over the
22 matches
Mail list logo