is all the text being indexed? Check to make sure that there's actually the
data you are looking for in the index. Is there a setting in tika that
limits how much is indexed? I seem to remember confronting this problem
myself once, and the data that I wanted just wasn't in the index because it
was
Do a search with the same criteria before and after?
On Wed, Sep 2, 2015 at 3:30 PM, Renee Sun wrote:
> I run this curl trying to delete some messages :
>
> curl
> 'http://localhost:8080/solr/mycore/update?commit=true&stream.body=
> abacd'
> | xmllint --format -
>
> or
>
> curl
> 'http://localho
time":0.0},
"debug":{
"time":0.0}},
"process":{
"time":23.0,
"query":{
"time":14.0},
"facet":{
"time":0.0},
"facet_module":{
to be highlighted. This will avoid having to run documents through
> the analysis chain at query-time and will make highlighting significantly
> faster and use less memory, particularly for large text fields, and even
> more so when hl.usePhraseHighlighter is enabled."
>
> So y
r&wt=json&indent=true&hl=true&hl.fl=text&hl.simple.pre=%3Cem%3E&hl.simple.post=%3C%2Fem%3E
used to produce snippets of highlited text in 4.6. In 5.2 it does not.
Thanks -
Mark Ehle
Computer Support Librarian
Willard Library
Battle Creek, MI
On Tue, Jun 30, 2015 at 10
om> wrote:
> >
> >> Actually storing or not storing a field is a simple schema.xml
> >> configuration.
> >> This suggestion can be obvious, but … have you checked you have your
> >> "stored" attribute set "true" for the field you are
ring or not storing a field is a simple schema.xml
> configuration.
> This suggestion can be obvious, but … have you checked you have your
> "stored" attribute set "true" for the field you are interested ?
>
> I am talking about the 5.2 schema.
>
> Cheers
>
&g
highlighting so I need the text there.
What would be different about 5.2 that would account for this?
Thanks!
Mark Ehle
Computer Support Librarian
Willard Library
Battle Creek,MI
