Re: faceting is unusable slow since upgrade to 5.3.0

[William Bell]

Same question here

Wondering if faceting performance is fixed and how to take advantage of it ?

On Wed, Dec 16, 2015 at 2:57 AM, Vincenzo D'Amore 
wrote:

> Hi all,
>
> given that solr 5.4 is finally released, is this what's more stable and
> efficient version of solrcloud ?
>
> I have a website which receives many search requests. It serve normally
> about 2000 concurrent requests, but sometime there are peak from 4000 to
> 1 requests in few seconds.
>
> On January I'll have a chance to upgrade my old SolrCloud 4.8.1 cluster to
> a new brand version, but following this thread I read about the problems
> that can occur upgrading to latest version.
>
> I have seen that issue SOLR-7730 "speed-up faceting on doc values fields"
> is fixed in 5.4.
>
> I'm using standard faceting without docValues. Should I add docValues in
> order to benefit of such fix?
>
> Best regards,
> Vincenzo
>
>
>
> On Thu, Oct 8, 2015 at 2:22 PM, Mikhail Khludnev <
> mkhlud...@griddynamics.com
> > wrote:
>
> > Uwe, it's good to know! I mean that you've recovered. Take care!
> >
> > On Thu, Oct 8, 2015 at 1:24 PM, Uwe Reh 
> > wrote:
> >
> > > Sorry for the delay. I had an ugly flu.
> > >
> > > SOLR-7730 seems to work fine. Using docValues with Solr
> > > 5.4.0-2015-09-29_08-29-55 1705813 makes my faceted queries fast again.
> > > (90ms vs. 2ms) :-)
> > >
> > > Thanks
> > > Uwe
> > >
> > >
> > >
> > >
> > > Am 27.09.2015 um 20:32 schrieb Mikhail Khludnev:
> > >
> > >> On Sun, Sep 27, 2015 at 2:00 PM, Uwe Reh 
> > >> wrote:
> > >>
> > >> When 5.4 with SOLR-7730 will be released, I will start to use
> docValues.
> > >>> Going this way, seems more straight forward to me.
> > >>>
> > >>
> > >>
> > >> Sure. Giving your answers docValues facets has a really good chance to
> > >> perform in your index after SOLR-7730. It's really interesting to see
> > >> performance numbers on early 5.4 builds:
> > >>
> > >>
> >
> https://builds.apache.org/view/All/job/Solr-Artifacts-5.x/lastSuccessfulBuild/artifact/solr/package/
> > >>
> > >>
> > >
> >
> >
> > --
> > Sincerely yours
> > Mikhail Khludnev
> > Principal Engineer,
> > Grid Dynamics
> >
> > 
> > 
> >
>
>
>
> --
> Vincenzo D'Amore
> email: v.dam...@gmail.com
> skype: free.dev
> mobile: +39 349 8513251
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: faceting is unusable slow since upgrade to 5.3.0

[William Bell]

Can we add method=uif back when not using the JSON Facet API too?

That would help a lot of people.

On Thu, Dec 17, 2015 at 7:17 AM, Yonik Seeley  wrote:

> On Wed, Dec 16, 2015 at 4:57 AM, Vincenzo D'Amore 
> wrote:
> > Hi all,
> >
> > given that solr 5.4 is finally released, is this what's more stable and
> > efficient version of solrcloud ?
> >
> > I have a website which receives many search requests. It serve normally
> > about 2000 concurrent requests, but sometime there are peak from 4000 to
> > 1 requests in few seconds.
> >
> > On January I'll have a chance to upgrade my old SolrCloud 4.8.1 cluster
> to
> > a new brand version, but following this thread I read about the problems
> > that can occur upgrading to latest version.
> >
> > I have seen that issue SOLR-7730 "speed-up faceting on doc values fields"
> > is fixed in 5.4.
> >
> > I'm using standard faceting without docValues. Should I add docValues in
> > order to benefit of such fix?
>
> You'll have to try it I think...
> DocValues have a lot of advantages (much less heap consumption, and
> much smaller overhead when opening a new searcher), but they can often
> be slower as well.
>
> Comparing 4x to 5x non-docvalues, top-level field caches were removed
> by lucene, and while that benefits certain things like NRT (opening a
> new searcher very often), it will hurt performance for other
> configurations.
>
> The JSON Facet API currently allows you to pick your strategy via the
> "method" param for multi-valued string fields without docvalues:
> "uif" (UninvertedField) gets you the top-level strategy from Solr 4,
> while "dv" (DocValues built on-the-fly) gets you the NRT-friendly
> "per-segment" strategy.
>
> -Yonik
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: faceting is unusable slow since upgrade to 5.3.0

[William Bell]

Thanks Jamie.

On Sat, Dec 19, 2015 at 11:31 PM, Jamie Johnson  wrote:

> Bill,
>
> Check out the patch attached to
> https://issues.apache.org/jira/browse/SOLR-8096.  I had considered making
> the method uif after I had done most of the work, it would be trivial to
> change and would probably be more aligned with not adding unexpected
> changes to people that are currently using fc.
>
> -Jamie
>
> On Sat, Dec 19, 2015 at 11:03 PM, William Bell 
> wrote:
>
> > Can we add method=uif back when not using the JSON Facet API too?
> >
> > That would help a lot of people.
> >
> > On Thu, Dec 17, 2015 at 7:17 AM, Yonik Seeley  wrote:
> >
> > > On Wed, Dec 16, 2015 at 4:57 AM, Vincenzo D'Amore 
> > > wrote:
> > > > Hi all,
> > > >
> > > > given that solr 5.4 is finally released, is this what's more stable
> and
> > > > efficient version of solrcloud ?
> > > >
> > > > I have a website which receives many search requests. It serve
> normally
> > > > about 2000 concurrent requests, but sometime there are peak from 4000
> > to
> > > > 1 requests in few seconds.
> > > >
> > > > On January I'll have a chance to upgrade my old SolrCloud 4.8.1
> cluster
> > > to
> > > > a new brand version, but following this thread I read about the
> > problems
> > > > that can occur upgrading to latest version.
> > > >
> > > > I have seen that issue SOLR-7730 "speed-up faceting on doc values
> > fields"
> > > > is fixed in 5.4.
> > > >
> > > > I'm using standard faceting without docValues. Should I add docValues
> > in
> > > > order to benefit of such fix?
> > >
> > > You'll have to try it I think...
> > > DocValues have a lot of advantages (much less heap consumption, and
> > > much smaller overhead when opening a new searcher), but they can often
> > > be slower as well.
> > >
> > > Comparing 4x to 5x non-docvalues, top-level field caches were removed
> > > by lucene, and while that benefits certain things like NRT (opening a
> > > new searcher very often), it will hurt performance for other
> > > configurations.
> > >
> > > The JSON Facet API currently allows you to pick your strategy via the
> > > "method" param for multi-valued string fields without docvalues:
> > > "uif" (UninvertedField) gets you the top-level strategy from Solr 4,
> > > while "dv" (DocValues built on-the-fly) gets you the NRT-friendly
> > > "per-segment" strategy.
> > >
> > > -Yonik
> > >
> >
> >
> >
> > --
> > Bill Bell
> > billnb...@gmail.com
> > cell 720-256-8076
> >
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Best practices on monitoring Solr

[William Bell]

Sematext.com has a service for this...

Or just curl "http://localhost:8983/solr//select?q=*:*" to see
if it returns ?

On Tue, Dec 22, 2015 at 12:15 PM, Tiwari, Shailendra <
shailendra.tiw...@macmillan.com> wrote:

> Hi,
>
> Last week our Solr Search was un-responsive and we need to re-boot the
> server, but we were able to find out after customer complained about it.
> What's best way to monitor that search is working?
> We can always add Gomez alerts from UI.
> What are the best practices?
>
> Thanks
>
> Shail




-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: How to check when a search exceeds the threshold of timeAllowed parameter

[William Bell]

I agree that when using timeAllowed in the header info there should be an
entry that indicates timeAllowed triggered.
This is the only reason why we have not used timeAllowed. So this is a
great suggestion. Something like: 1 ??
That would be great.


0
1
107

*:*
1000





On Tue, Dec 22, 2015 at 6:43 PM, Vincenzo D'Amore 
wrote:

> Well... I can write everything, but really all this just to understand
> when timeAllowed
> parameter trigger a partial answer? I mean, isn't there anything set in the
> response when is partial?
>
> On Wed, Dec 23, 2015 at 2:38 AM, Walter Underwood 
> wrote:
>
> > We need to know a LOT more about your site. Number of documents, size of
> > index, frequency of updates, length of queries approximate size of server
> > (CPUs, RAM, type of disk), version of Solr, version of Java, and features
> > you are using (faceting, highlighting, etc.).
> >
> > After that, we’ll have more questions.
> >
> > wunder
> > Walter Underwood
> > wun...@wunderwood.org
> > http://observer.wunderwood.org/  (my blog)
> >
> >
> > > On Dec 22, 2015, at 4:58 PM, Vincenzo D'Amore 
> > wrote:
> > >
> > > Hi All,
> > >
> > > my website is under pressure, there is a big number of concurrent
> > searches.
> > > When the connected users are too many, the searches becomes so slow
> that
> > in
> > > some cases users have to wait many seconds.
> > > The queue of searches becomes so long that, in same cases, servers are
> > > blocked trying to serve all these requests.
> > > As far as I know because some searches are very expensive, and when
> many
> > > expensive searches clog the queue server becomes unresponsive.
> > >
> > > In order to quickly workaround this herd effect, I have added a
> > > default timeAllowed to 15 seconds, and this seems help a lot.
> > >
> > > But during stress tests but I'm unable to understand when and what
> > requests
> > > are affected by timeAllowed parameter.
> > >
> > > Just be clear, I have configure timeAllowed parameter in a SolrCloud
> > > environment, given that partial results may be returned (if there are
> > any),
> > > how can I know when this happens? When the timeAllowed parameter
> trigger
> > a
> > > partial answer?
> > >
> > > Best regards,
> > > Vincenzo
> > >
> > >
> > >
> > > --
> > > Vincenzo D'Amore
> > > email: v.dam...@gmail.com
> > > skype: free.dev
> > > mobile: +39 349 8513251
> >
> >
>
>
> --
> Vincenzo D'Amore
> email: v.dam...@gmail.com
> skype: free.dev
> mobile: +39 349 8513251
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: API accessible without authentication even though Basic Auth Plugin is enabled

[William Bell]

Why would someone stay on 5.3.x instead of upgrading to 5.4? Why backport
when you can just upgrade?

On Tue, Dec 22, 2015 at 6:33 PM, Noble Paul  wrote:

> A 5.3.2 release is coming up which will back port the fixes introduced in
> 5.4
> On Dec 17, 2015 10:25 PM, "tine-2"  wrote:
>
> > Noble Paul നോബിള്‍  नोब्ळ् wrote
> > > It works as designed.
> > >
> > > Protect the read path [...]
> >
> > Works like described in 5.4.0, didn't work in 5.3.1, s.
> > https://issues.apache.org/jira/browse/SOLR-8408
> >
> >
> >
> > --
> > View this message in context:
> >
> http://lucene.472066.n3.nabble.com/API-accessible-without-authentication-even-though-Basic-Auth-Plugin-is-enabled-tp4244940p4246099.html
> > Sent from the Solr - User mailing list archive at Nabble.com.
> >
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: How to check when a search exceeds the threshold of timeAllowed parameter

[William Bell]

Great I must have missed that.

On Wed, Dec 23, 2015 at 9:41 AM, Jeff Wartes  wrote:

> Looks like it’ll set partialResults=true on your results if you hit the
> timeout.
>
> https://issues.apache.org/jira/browse/SOLR-502
>
> https://issues.apache.org/jira/browse/SOLR-5986
>
>
>
>
>
>
> On 12/22/15, 5:43 PM, "Vincenzo D'Amore"  wrote:
>
> >Well... I can write everything, but really all this just to understand
> >when timeAllowed
> >parameter trigger a partial answer? I mean, isn't there anything set in
> the
> >response when is partial?
> >
> >On Wed, Dec 23, 2015 at 2:38 AM, Walter Underwood 
> >wrote:
> >
> >> We need to know a LOT more about your site. Number of documents, size of
> >> index, frequency of updates, length of queries approximate size of
> server
> >> (CPUs, RAM, type of disk), version of Solr, version of Java, and
> features
> >> you are using (faceting, highlighting, etc.).
> >>
> >> After that, we’ll have more questions.
> >>
> >> wunder
> >> Walter Underwood
> >> wun...@wunderwood.org
> >> http://observer.wunderwood.org/  (my blog)
> >>
> >>
> >> > On Dec 22, 2015, at 4:58 PM, Vincenzo D'Amore 
> >> wrote:
> >> >
> >> > Hi All,
> >> >
> >> > my website is under pressure, there is a big number of concurrent
> >> searches.
> >> > When the connected users are too many, the searches becomes so slow
> that
> >> in
> >> > some cases users have to wait many seconds.
> >> > The queue of searches becomes so long that, in same cases, servers are
> >> > blocked trying to serve all these requests.
> >> > As far as I know because some searches are very expensive, and when
> many
> >> > expensive searches clog the queue server becomes unresponsive.
> >> >
> >> > In order to quickly workaround this herd effect, I have added a
> >> > default timeAllowed to 15 seconds, and this seems help a lot.
> >> >
> >> > But during stress tests but I'm unable to understand when and what
> >> requests
> >> > are affected by timeAllowed parameter.
> >> >
> >> > Just be clear, I have configure timeAllowed parameter in a SolrCloud
> >> > environment, given that partial results may be returned (if there are
> >> any),
> >> > how can I know when this happens? When the timeAllowed parameter
> trigger
> >> a
> >> > partial answer?
> >> >
> >> > Best regards,
> >> > Vincenzo
> >> >
> >> >
> >> >
> >> > --
> >> > Vincenzo D'Amore
> >> > email: v.dam...@gmail.com
> >> > skype: free.dev
> >> > mobile: +39 349 8513251
> >>
> >>
> >
> >
> >--
> >Vincenzo D'Amore
> >email: v.dam...@gmail.com
> >skype: free.dev
> >mobile: +39 349 8513251
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Issue with Join

[William Bell]

I have having issues with {!join}. If the core have multiValued field and
the inner join does not have a multiValued field it does not find the
ones...

Solr 5.3.1... 5.3.1

Example.

PS1226 is in practicing_specialties_codes in providersearch core. This
field is multiValued.

in the autosuggest core there is NOT a field for PS1226 in there. This
field is called prac_spec_code and is single values.


http://localhost:8983/solr/providersearch/select?q=*%3A*&wt=json&indent=true&fq=practicing_specialties_codes:PS1226&fl=practicing_specialties_codes

I get:


   - docs:
   [
  -
  {
 - practicing_specialties_codes:
 [
- "PS1010",
- "PS282",
- "PS1226"
]
 }
  ]



In autosuggest there is nothing:

http://localhost:8983/solr/autosuggest/select?q=*%3A*&wt=json&indent=true&fq=prac_spec_code:PS1226&fl=prac_spec_code

Nothing.

Then a join should find what is in providersearch but missing in
autosuggest.

http://localhost:8983/solr/providersearch/select?debugQuery=true&wt=json&q=*:*&rows=10&fq=practicing_specialties_codes:PS1226&fl=practicing_specialties_codes&fq=NOT%20{!join%20from=prac_spec_code%20to=practicing_specialties_codes%20fromIndex=autosuggest}auto_type:PRACSPEC

or

http://hgsolr2sl1:8983/solr/providersearch/select?debugQuery=true&wt=json&q=*:*&rows=10&fl=practicing_specialties_codes&fq=NOT%20{!join%20from=prac_spec_code%20to=practicing_specialties_codes%20fromIndex=autosuggest}auto_type:PRACSPEC

or

http://hgsolr2sl1:8983/solr/providersearch/select?debugQuery=true&wt=json&q=*:*&rows=10&fl=practicing_specialties_codes&fq=NOT%20{!join%20from=prac_spec_code%20to=practicing_specialties_codes%20fromIndex=autosuggest}*:*

I also tried *:* AND NOT {!join}

I get 0 results. This seems to be a bug.

{

   - responseHeader:
   {
  - status: 0,
  - QTime: 178,
  - params:
  {
 - q: "*:*",
 - fl: "practicing_specialties_codes",
 - fq: "NOT {!join from=prac_spec_code
 to=practicing_specialties_codes fromIndex=autosuggest}*:*",
 - rows: "10",
 - wt: "json",
 - debugQuery: "true"
 }
  },
   - response:
   {
  - numFound: 0,
  - start: 0,
  - docs: [ ]
  },
   - debug:
   {
  - rawquerystring: "*:*",
  - querystring: "*:*",
  - parsedquery: "MatchAllDocsQuery(*:*)",
  - parsedquery_toString: "*:*",
  - explain: { },
  - QParser: "LuceneQParser",
  - filter_queries:
  [
 - "NOT {!join from=prac_spec_code to=practicing_specialties_codes
 fromIndex=autosuggest}*:*"
 ],
  - parsed_filter_queries:
  [
 - "-JoinQuery({!join from=prac_spec_code
 to=practicing_specialties_codes fromIndex=autosuggest}*:*)"
 ],
  - timing:
  {
 - time: 177,
 - prepare:
 {
- time: 0,
- query:
{
   - time: 0
   },
- facet:
{
   - time: 0
   },
- facet_module:
{
   - time: 0
   },
- mlt:
{
   - time: 0
   },
- highlight:
{
   - time: 0
   },
- stats:
{
   - time: 0
   },
- expand:
{
   - time: 0
   },
- debug:
{
   - time: 0
   }
},
 - process:
 {
- time: 177,
- query:
{
   - time: 177
   },
- facet:
{
   - time: 0
   },
- facet_module:
{
   - time: 0
   },
- mlt:
{
   - time: 0
   },
- highlight:
{
   - time: 0
   },
- stats:
{
   - time: 0
   },
- expand:
{
   - time: 0
   },
- debug:
{
   - time: 0
   }
}
 }
  }

}




-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Issue with Join

[William Bell]

Thoughts?

I can duplicate it at will...

On Mon, Dec 28, 2015 at 9:02 PM, William Bell  wrote:

> I have having issues with {!join}. If the core have multiValued field and
> the inner join does not have a multiValued field it does not find the
> ones...
>
> Solr 5.3.1... 5.3.1
>
> Example.
>
> PS1226 is in practicing_specialties_codes in providersearch core. This
> field is multiValued.
>
> in the autosuggest core there is NOT a field for PS1226 in there. This
> field is called prac_spec_code and is single values.
>
>
>
> http://localhost:8983/solr/providersearch/select?q=*%3A*&wt=json&indent=true&fq=practicing_specialties_codes:PS1226&fl=practicing_specialties_codes
>
> I get:
>
>
>- docs:
>[
>   -
>   {
>  - practicing_specialties_codes:
>  [
> - "PS1010",
> - "PS282",
> - "PS1226"
> ]
>  }
>   ]
>
>
>
> In autosuggest there is nothing:
>
>
> http://localhost:8983/solr/autosuggest/select?q=*%3A*&wt=json&indent=true&fq=prac_spec_code:PS1226&fl=prac_spec_code
>
> Nothing.
>
> Then a join should find what is in providersearch but missing in
> autosuggest.
>
>
> http://localhost:8983/solr/providersearch/select?debugQuery=true&wt=json&q=*:*&rows=10&fq=practicing_specialties_codes:PS1226&fl=practicing_specialties_codes&fq=NOT%20{!join%20from=prac_spec_code%20to=practicing_specialties_codes%20fromIndex=autosuggest}auto_type:PRACSPEC
> <http://localhost:8983/solr/providersearch/select?debugQuery=true&wt=json&q=*:*&rows=10&fq=practicing_specialties_codes:PS1226&fl=practicing_specialties_codes&fq=NOT%20%7B!join%20from=prac_spec_code%20to=practicing_specialties_codes%20fromIndex=autosuggest%7Dauto_type:PRACSPEC>
>
> or
>
>
> http://hgsolr2sl1:8983/solr/providersearch/select?debugQuery=true&wt=json&q=*:*&rows=10&fl=practicing_specialties_codes&fq=NOT%20{!join%20from=prac_spec_code%20to=practicing_specialties_codes%20fromIndex=autosuggest}auto_type:PRACSPEC
> <http://hgsolr2sl1:8983/solr/providersearch/select?debugQuery=true&wt=json&q=*:*&rows=10&fl=practicing_specialties_codes&fq=NOT%20%7B!join%20from=prac_spec_code%20to=practicing_specialties_codes%20fromIndex=autosuggest%7Dauto_type:PRACSPEC>
>
> or
>
>
> http://hgsolr2sl1:8983/solr/providersearch/select?debugQuery=true&wt=json&q=*:*&rows=10&fl=practicing_specialties_codes&fq=NOT%20{!join%20from=prac_spec_code%20to=practicing_specialties_codes%20fromIndex=autosuggest}*:*
> <http://hgsolr2sl1:8983/solr/providersearch/select?debugQuery=true&wt=json&q=*:*&rows=10&fl=practicing_specialties_codes&fq=NOT%20%7B!join%20from=prac_spec_code%20to=practicing_specialties_codes%20fromIndex=autosuggest%7D*:*>
>
> I also tried *:* AND NOT {!join}
>
> I get 0 results. This seems to be a bug.
>
> {
>
>- responseHeader:
>{
>   - status: 0,
>   - QTime: 178,
>   - params:
>   {
>  - q: "*:*",
>  - fl: "practicing_specialties_codes",
>  - fq: "NOT {!join from=prac_spec_code
>  to=practicing_specialties_codes fromIndex=autosuggest}*:*",
>  - rows: "10",
>  - wt: "json",
>  - debugQuery: "true"
>  }
>   },
>- response:
>{
>   - numFound: 0,
>   - start: 0,
>   - docs: [ ]
>   },
>- debug:
>{
>   - rawquerystring: "*:*",
>   - querystring: "*:*",
>   - parsedquery: "MatchAllDocsQuery(*:*)",
>   - parsedquery_toString: "*:*",
>   - explain: { },
>   - QParser: "LuceneQParser",
>   - filter_queries:
>   [
>  - "NOT {!join from=prac_spec_code
>  to=practicing_specialties_codes fromIndex=autosuggest}*:*"
>  ],
>   - parsed_filter_queries:
>   [
>  - "-JoinQuery({!join from=prac_spec_code
>  to=practicing_specialties_codes fromIndex=autosuggest}*:*)"
>  ],
>   - timing:
>   {
>  - time: 177,
>  - prepare:
>  {
> - time: 0,
> - query:
> {
>- time: 0
>},
> - facet:
> {
>- time: 0
>},
> - facet_module:
> {
>- time: 0
>},
> - mlt:
> {
&

Re: Memory Usage increases by a lot during and after optimization .

[William Bell]

Question: does anyone have example good merge settings for solrconfig ? To
keep the number of segments small like 6?

On Tue, Dec 29, 2015 at 8:49 PM, Yonik Seeley  wrote:

> Some people also want to control when major segment merges happen, and
> optimizing at a known time helps prevent a major merge at an unknown
> time (which can be equivalent to an optimize/forceMerge).
>
> The benefits of optimizing (and having fewer segments to search
> across) will vary depending on the requests.
> Normal full-text searches will see little benefit (merging a few terms
> across many segments is not expensive), while other operations that
> need to deal with many terms, like faceting, may see bigger speedups.
>
> -Yonik
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Issue with Join

[William Bell]

Yeah I ran it. It appears to only have an issue if the field for the core
on the outside is MultiValue, and the inside field is single value, and the
order of the field has the code not as the first entry. Like:

 practicing_specialties_codes:
>  [
> - "PS1010",
> - "PS282",
> - "*PS1226*"
> ]
>  }

Here is the output of the debug:


   - join:
   {
  - {!join from=prac_spec_code to=practicing_specialties_codes
  fromIndex=autosuggest}*:*:
  {
 - time: 24,
 - fromSetSize: 170179,
 - toSetSize: 3194542,
 - fromTermCount: 1091,
 - fromTermTotalDf: 1091,
 - fromTermDirectCount: 1091,
 - fromTermHits: 1091,
 - fromTermHitsTotalDf: 1091,
 - toTermHits: 1069,
 - toTermHitsTotalDf: 4002538,
 - toTermDirectCount: 697,
 - smallSetsDeferred: 1,
 - toSetDocsAdded: 4002538
 }
  },


On Wed, Dec 30, 2015 at 2:02 AM, Mikhail Khludnev <
mkhlud...@griddynamics.com> wrote:

> Hello,
>
> Have you considered to pass NOT {!join from=prac_spec_code
> to=practicing_specialties_codes
>  fromIndex=autosuggest}*:* as a q and look at debug output.
> Also there was a trick for dealing with pure negative queries q=*:*
> -foo:bar though it might be obsolete.
>
> On Tue, Dec 29, 2015 at 7:02 AM, William Bell  wrote:
>
> > I have having issues with {!join}. If the core have multiValued field and
> > the inner join does not have a multiValued field it does not find the
> > ones...
> >
> > Solr 5.3.1... 5.3.1
> >
> > Example.
> >
> > PS1226 is in practicing_specialties_codes in providersearch core. This
> > field is multiValued.
> >
> > in the autosuggest core there is NOT a field for PS1226 in there. This
> > field is called prac_spec_code and is single values.
> >
> >
> >
> >
> http://localhost:8983/solr/providersearch/select?q=*%3A*&wt=json&indent=true&fq=practicing_specialties_codes:PS1226&fl=practicing_specialties_codes
> >
> > I get:
> >
> >
> >- docs:
> >[
> >   -
> >   {
> >  - practicing_specialties_codes:
> >  [
> > - "PS1010",
> > - "PS282",
> > - "PS1226"
> > ]
> >  }
> >   ]
> >
> >
> >
> > In autosuggest there is nothing:
> >
> >
> >
> http://localhost:8983/solr/autosuggest/select?q=*%3A*&wt=json&indent=true&fq=prac_spec_code:PS1226&fl=prac_spec_code
> >
> > Nothing.
> >
> > Then a join should find what is in providersearch but missing in
> > autosuggest.
> >
> >
> >
> http://localhost:8983/solr/providersearch/select?debugQuery=true&wt=json&q=*:*&rows=10&fq=practicing_specialties_codes:PS1226&fl=practicing_specialties_codes&fq=NOT%20{!join%20from=prac_spec_code%20to=practicing_specialties_codes%20fromIndex=autosuggest}auto_type:PRACSPEC
> >
> > or
> >
> >
> >
> http://hgsolr2sl1:8983/solr/providersearch/select?debugQuery=true&wt=json&q=*:*&rows=10&fl=practicing_specialties_codes&fq=NOT%20{!join%20from=prac_spec_code%20to=practicing_specialties_codes%20fromIndex=autosuggest}auto_type:PRACSPEC
> >
> > or
> >
> >
> >
> http://hgsolr2sl1:8983/solr/providersearch/select?debugQuery=true&wt=json&q=*:*&rows=10&fl=practicing_specialties_codes&fq=NOT%20{!join%20from=prac_spec_code%20to=practicing_specialties_codes%20fromIndex=autosuggest}*:*
> >
> > I also tried *:* AND NOT {!join}
> >
> > I get 0 results. This seems to be a bug.
> >
> > {
> >
> >- responseHeader:
> >{
> >   - status: 0,
> >   - QTime: 178,
> >   - params:
> >   {
> >  - q: "*:*",
> >  - fl: "practicing_specialties_codes",
> >  - fq: "NOT {!join from=prac_spec_code
> >  to=practicing_specialties_codes fromIndex=autosuggest}*:*",
> >  - rows: "10",
> >  - wt: "json",
> >  - debugQuery: "true"
> >  }
> >   },
> >- response:
> >{
> >   - numFound: 0,
> >   - start: 0,
> >   - docs: [ ]
> >   },
> >- debug:
> >{
> >   - rawquerystring: "*:*",
> >   - querystring: "*:*",
> >   - pa

SOLR 5.4.0?

[William Bell]

How is SOLR 5.4.0 ? I heard there was a quick 5.4.1 coming out?

Any major issues?

-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Issue with if() statement

[William Bell]

We are getting weird results with if(exists(a),b,c). We are getting b+c!!

http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),{!lucene%20v=$state1},{!lucene%20v=$state})

I am getting NY and CO!

I only want $state1, which is NY.

Any other ways to craft this?


-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Issue with if() statement

[William Bell]

Sure.

If the state:NY returns results filter by state:NY, if it does not, then
use state:CO. If we have results in NY, use it, otherwise use CO.

OK?

On Fri, Jan 1, 2016 at 1:15 PM, Upayavira  wrote:

>
>
> On Thu, Dec 31, 2015, at 11:50 PM, William Bell wrote:
> > We are getting weird results with if(exists(a),b,c). We are getting b+c!!
> >
> >
> http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),{!lucene%20v=$state1},{!lucene%20v=$state})
> >
> > I am getting NY and CO!
> >
> > I only want $state1, which is NY.
> >
> > Any other ways to craft this?
>
> Does this work at all?
>
> The if() function is a function query that can be used to sort, boost
> and as calculated fields. I haven't seen them used in filtering.
>
> Also, the query() function does *not* do a query, it just says "what
> would this document score for this query?"
>
> Can you describe in English what you are trying to do?
>
> Upayavira
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Issue with if() statement

[William Bell]

Example.

http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state1}

This return 236,000

http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state}

This returns 10,000

I want to put an IF statement around which v to use.






On Fri, Jan 1, 2016 at 1:52 PM, William Bell  wrote:

> Sure.
>
> If the state:NY returns results filter by state:NY, if it does not, then
> use state:CO. If we have results in NY, use it, otherwise use CO.
>
> OK?
>
> On Fri, Jan 1, 2016 at 1:15 PM, Upayavira  wrote:
>
>>
>>
>> On Thu, Dec 31, 2015, at 11:50 PM, William Bell wrote:
>> > We are getting weird results with if(exists(a),b,c). We are getting
>> b+c!!
>> >
>> >
>> http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),{!lucene%20v=$state1},{!lucene%20v=$state})
>> <http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),%7B!lucene%20v=$state1%7D,%7B!lucene%20v=$state%7D)>
>> >
>> > I am getting NY and CO!
>> >
>> > I only want $state1, which is NY.
>> >
>> > Any other ways to craft this?
>>
>> Does this work at all?
>>
>> The if() function is a function query that can be used to sort, boost
>> and as calculated fields. I haven't seen them used in filtering.
>>
>> Also, the query() function does *not* do a query, it just says "what
>> would this document score for this query?"
>>
>> Can you describe in English what you are trying to do?
>>
>> Upayavira
>>
>
>
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 720-256-8076
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Issue with if() statement

[William Bell]

Another weirdness:

http://localhost:8983/solr/providersearch/select?wt=json&state=state:CO&state1=state:NY&fl=*&q=*:*&tt=$state1&fq={!lucene%20v=$tt}

That does not return anything.

But if I set v=$state1 I get results.

Can I not set equivalent variables?



On Fri, Jan 1, 2016 at 2:07 PM, William Bell  wrote:

> Example.
>
>
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state1}
> <http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq=%7B!lucene%20v=$state1%7D>
>
> This return 236,000
>
>
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state}
> <http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq=%7B!lucene%20v=$state%7D>
>
> This returns 10,000
>
> I want to put an IF statement around which v to use.
>
>
>
>
>
>
> On Fri, Jan 1, 2016 at 1:52 PM, William Bell  wrote:
>
>> Sure.
>>
>> If the state:NY returns results filter by state:NY, if it does not, then
>> use state:CO. If we have results in NY, use it, otherwise use CO.
>>
>> OK?
>>
>> On Fri, Jan 1, 2016 at 1:15 PM, Upayavira  wrote:
>>
>>>
>>>
>>> On Thu, Dec 31, 2015, at 11:50 PM, William Bell wrote:
>>> > We are getting weird results with if(exists(a),b,c). We are getting
>>> b+c!!
>>> >
>>> >
>>> http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),{!lucene%20v=$state1},{!lucene%20v=$state})
>>> <http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),%7B!lucene%20v=$state1%7D,%7B!lucene%20v=$state%7D)>
>>> >
>>> > I am getting NY and CO!
>>> >
>>> > I only want $state1, which is NY.
>>> >
>>> > Any other ways to craft this?
>>>
>>> Does this work at all?
>>>
>>> The if() function is a function query that can be used to sort, boost
>>> and as calculated fields. I haven't seen them used in filtering.
>>>
>>> Also, the query() function does *not* do a query, it just says "what
>>> would this document score for this query?"
>>>
>>> Can you describe in English what you are trying to do?
>>>
>>> Upayavira
>>>
>>
>>
>>
>> --
>> Bill Bell
>> billnb...@gmail.com
>> cell 720-256-8076
>>
>
>
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 720-256-8076
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Issue with if() statement

[William Bell]

This all started with me trying to use {!switch} to indicate with CO or NY
to use. if we pass state1, that is supposed to take precedence, but if
nothing is returned, then use state Make sense now?

I could not find a way to check for strlen($state1). Which is what I want
in the case statement. This just does not work...
Something like the following is what I am trying to do:


fq={!switch case."anything"=$state1
default=$state
 v=$state1}

So I tried the following to set all 50 states:


fq={!switch case.all='*:*'
 case.CO='state:CO'
 case.NY='state:NY'
 v=$state1}


Obviously Oregon (OR!) is an issue, and it won't work at all plus



On Fri, Jan 1, 2016 at 2:15 PM, William Bell  wrote:

> Another weirdness:
>
>
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:CO&state1=state:NY&fl=*&q=*:*&tt=$state1&fq={!lucene%20v=$tt}
> <http://localhost:8983/solr/providersearch/select?wt=json&state=state:CO&state1=state:NY&fl=*&q=*:*&tt=$state1&fq=%7B!lucene%20v=$tt%7D>
>
> That does not return anything.
>
> But if I set v=$state1 I get results.
>
> Can I not set equivalent variables?
>
>
>
> On Fri, Jan 1, 2016 at 2:07 PM, William Bell  wrote:
>
>> Example.
>>
>>
>> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state1}
>> <http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq=%7B!lucene%20v=$state1%7D>
>>
>> This return 236,000
>>
>>
>> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state}
>> <http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq=%7B!lucene%20v=$state%7D>
>>
>> This returns 10,000
>>
>> I want to put an IF statement around which v to use.
>>
>>
>>
>>
>>
>>
>> On Fri, Jan 1, 2016 at 1:52 PM, William Bell  wrote:
>>
>>> Sure.
>>>
>>> If the state:NY returns results filter by state:NY, if it does not, then
>>> use state:CO. If we have results in NY, use it, otherwise use CO.
>>>
>>> OK?
>>>
>>> On Fri, Jan 1, 2016 at 1:15 PM, Upayavira  wrote:
>>>
>>>>
>>>>
>>>> On Thu, Dec 31, 2015, at 11:50 PM, William Bell wrote:
>>>> > We are getting weird results with if(exists(a),b,c). We are getting
>>>> b+c!!
>>>> >
>>>> >
>>>> http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),{!lucene%20v=$state1},{!lucene%20v=$state})
>>>> <http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),%7B!lucene%20v=$state1%7D,%7B!lucene%20v=$state%7D)>
>>>> >
>>>> > I am getting NY and CO!
>>>> >
>>>> > I only want $state1, which is NY.
>>>> >
>>>> > Any other ways to craft this?
>>>>
>>>> Does this work at all?
>>>>
>>>> The if() function is a function query that can be used to sort, boost
>>>> and as calculated fields. I haven't seen them used in filtering.
>>>>
>>>> Also, the query() function does *not* do a query, it just says "what
>>>> would this document score for this query?"
>>>>
>>>> Can you describe in English what you are trying to do?
>>>>
>>>> Upayavira
>>>>
>>>
>>>
>>>
>>> --
>>> Bill Bell
>>> billnb...@gmail.com
>>> cell 720-256-8076
>>>
>>
>>
>>
>> --
>> Bill Bell
>> billnb...@gmail.com
>> cell 720-256-8076
>>
>
>
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 720-256-8076
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Issue with if() statement

[William Bell]

Maybe we can add function value on a switch?

fq={!switch case.gt.0
 default=$state
 func=len($state1)}



We could add: gt, lt, eq, ge, le ?

gt: greater than
lt: less than
eq: equal
ge: greater than or equal
le: less than or equal

??



On Fri, Jan 1, 2016 at 2:25 PM, William Bell  wrote:

> This all started with me trying to use {!switch} to indicate with CO or NY
> to use. if we pass state1, that is supposed to take precedence, but if
> nothing is returned, then use state Make sense now?
>
> I could not find a way to check for strlen($state1). Which is what I want
> in the case statement. This just does not work...
> Something like the following is what I am trying to do:
>
>
> fq={!switch case."anything"=$state1
> default=$state
>  v=$state1}
>
> So I tried the following to set all 50 states:
>
>
> fq={!switch case.all='*:*'
>  case.CO='state:CO'
>  case.NY='state:NY'
>  v=$state1}
>
>
> Obviously Oregon (OR!) is an issue, and it won't work at all plus
>
>
>
> On Fri, Jan 1, 2016 at 2:15 PM, William Bell  wrote:
>
>> Another weirdness:
>>
>>
>> http://localhost:8983/solr/providersearch/select?wt=json&state=state:CO&state1=state:NY&fl=*&q=*:*&tt=$state1&fq={!lucene%20v=$tt}
>> <http://localhost:8983/solr/providersearch/select?wt=json&state=state:CO&state1=state:NY&fl=*&q=*:*&tt=$state1&fq=%7B!lucene%20v=$tt%7D>
>>
>> That does not return anything.
>>
>> But if I set v=$state1 I get results.
>>
>> Can I not set equivalent variables?
>>
>>
>>
>> On Fri, Jan 1, 2016 at 2:07 PM, William Bell  wrote:
>>
>>> Example.
>>>
>>>
>>> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state1}
>>> <http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq=%7B!lucene%20v=$state1%7D>
>>>
>>> This return 236,000
>>>
>>>
>>> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state}
>>> <http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq=%7B!lucene%20v=$state%7D>
>>>
>>> This returns 10,000
>>>
>>> I want to put an IF statement around which v to use.
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Jan 1, 2016 at 1:52 PM, William Bell 
>>> wrote:
>>>
>>>> Sure.
>>>>
>>>> If the state:NY returns results filter by state:NY, if it does not,
>>>> then use state:CO. If we have results in NY, use it, otherwise use CO.
>>>>
>>>> OK?
>>>>
>>>> On Fri, Jan 1, 2016 at 1:15 PM, Upayavira  wrote:
>>>>
>>>>>
>>>>>
>>>>> On Thu, Dec 31, 2015, at 11:50 PM, William Bell wrote:
>>>>> > We are getting weird results with if(exists(a),b,c). We are getting
>>>>> b+c!!
>>>>> >
>>>>> >
>>>>> http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),{!lucene%20v=$state1},{!lucene%20v=$state})
>>>>> <http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),%7B!lucene%20v=$state1%7D,%7B!lucene%20v=$state%7D)>
>>>>> >
>>>>> > I am getting NY and CO!
>>>>> >
>>>>> > I only want $state1, which is NY.
>>>>> >
>>>>> > Any other ways to craft this?
>>>>>
>>>>> Does this work at all?
>>>>>
>>>>> The if() function is a function query that can be used to sort, boost
>>>>> and as calculated fields. I haven't seen them used in filtering.
>>>>>
>>>>> Also, the query() function does *not* do a query, it just says "what
>>>>> would this document score for this query?"
>>>>>
>>>>> Can you describe in English what you are trying to do?
>>>>>
>>>>> Upayavira
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Bill Bell
>>>> billnb...@gmail.com
>>>> cell 720-256-8076
>>>>
>>>
>>>
>>>
>>> --
>>> Bill Bell
>>> billnb...@gmail.com
>>> cell 720-256-8076
>>>
>>
>>
>>
>> --
>> Bill Bell
>> billnb...@gmail.com
>> cell 720-256-8076
>>
>
>
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 720-256-8076
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Issue with if() statement

[William Bell]

Forgot last bit:

fq={!switch case.gt.0=$state1
 default=$state
 func=len($state1)}


On Fri, Jan 1, 2016 at 2:39 PM, William Bell  wrote:

> Maybe we can add function value on a switch?
>
> fq={!switch case.gt.0
>  default=$state
>  func=len($state1)}
>
>
>
> We could add: gt, lt, eq, ge, le ?
>
> gt: greater than
> lt: less than
> eq: equal
> ge: greater than or equal
> le: less than or equal
>
> ??
>
>
>
> On Fri, Jan 1, 2016 at 2:25 PM, William Bell  wrote:
>
>> This all started with me trying to use {!switch} to indicate with CO or
>> NY to use. if we pass state1, that is supposed to take precedence, but if
>> nothing is returned, then use state Make sense now?
>>
>> I could not find a way to check for strlen($state1). Which is what I want
>> in the case statement. This just does not work...
>> Something like the following is what I am trying to do:
>>
>>
>> fq={!switch case."anything"=$state1
>> default=$state
>>  v=$state1}
>>
>> So I tried the following to set all 50 states:
>>
>>
>> fq={!switch case.all='*:*'
>>  case.CO='state:CO'
>>      case.NY='state:NY'
>>  v=$state1}
>>
>>
>> Obviously Oregon (OR!) is an issue, and it won't work at all plus
>>
>>
>>
>> On Fri, Jan 1, 2016 at 2:15 PM, William Bell  wrote:
>>
>>> Another weirdness:
>>>
>>>
>>> http://localhost:8983/solr/providersearch/select?wt=json&state=state:CO&state1=state:NY&fl=*&q=*:*&tt=$state1&fq={!lucene%20v=$tt}
>>> <http://localhost:8983/solr/providersearch/select?wt=json&state=state:CO&state1=state:NY&fl=*&q=*:*&tt=$state1&fq=%7B!lucene%20v=$tt%7D>
>>>
>>> That does not return anything.
>>>
>>> But if I set v=$state1 I get results.
>>>
>>> Can I not set equivalent variables?
>>>
>>>
>>>
>>> On Fri, Jan 1, 2016 at 2:07 PM, William Bell 
>>> wrote:
>>>
>>>> Example.
>>>>
>>>>
>>>> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state1}
>>>> <http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq=%7B!lucene%20v=$state1%7D>
>>>>
>>>> This return 236,000
>>>>
>>>>
>>>> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state}
>>>> <http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq=%7B!lucene%20v=$state%7D>
>>>>
>>>> This returns 10,000
>>>>
>>>> I want to put an IF statement around which v to use.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Fri, Jan 1, 2016 at 1:52 PM, William Bell 
>>>> wrote:
>>>>
>>>>> Sure.
>>>>>
>>>>> If the state:NY returns results filter by state:NY, if it does not,
>>>>> then use state:CO. If we have results in NY, use it, otherwise use CO.
>>>>>
>>>>> OK?
>>>>>
>>>>> On Fri, Jan 1, 2016 at 1:15 PM, Upayavira  wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, Dec 31, 2015, at 11:50 PM, William Bell wrote:
>>>>>> > We are getting weird results with if(exists(a),b,c). We are getting
>>>>>> b+c!!
>>>>>> >
>>>>>> >
>>>>>> http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),{!lucene%20v=$state1},{!lucene%20v=$state})
>>>>>> <http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),%7B!lucene%20v=$state1%7D,%7B!lucene%20v=$state%7D)>
>>>>>> >
>>>>>> > I am getting NY and CO!
>>>>>> >
>>>>>> > I only want $state1, which is NY.
>>>>>> >
>>>>>> > Any other ways to craft this?
>>>>>>
>>>>>> Does this work at all?
>>>>>>
>>>>>> The if() function is a function query that can be used to sort, boost
>>>>>> and as calculated fields. I haven't seen them used in filtering.
>>>>>>
>>>>>> Also, the query() function does *not* do a query, it just says "what
>>>>>> would this document score for this query?"
>>>>>>
>>>>>> Can you describe in English what you are trying to do?
>>>>>>
>>>>>> Upayavira
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Bill Bell
>>>>> billnb...@gmail.com
>>>>> cell 720-256-8076
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Bill Bell
>>>> billnb...@gmail.com
>>>> cell 720-256-8076
>>>>
>>>
>>>
>>>
>>> --
>>> Bill Bell
>>> billnb...@gmail.com
>>> cell 720-256-8076
>>>
>>
>>
>>
>> --
>> Bill Bell
>> billnb...@gmail.com
>> cell 720-256-8076
>>
>
>
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 720-256-8076
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Issue with if() statement

[William Bell]

Also ne: not equal.

This is like KSH.

On Fri, Jan 1, 2016 at 2:40 PM, William Bell  wrote:

> Forgot last bit:
>
> fq={!switch case.gt.0=$state1
>  default=$state
>  func=len($state1)}
>
>
> On Fri, Jan 1, 2016 at 2:39 PM, William Bell  wrote:
>
>> Maybe we can add function value on a switch?
>>
>> fq={!switch case.gt.0
>>  default=$state
>>  func=len($state1)}
>>
>>
>>
>> We could add: gt, lt, eq, ge, le ?
>>
>> gt: greater than
>> lt: less than
>> eq: equal
>> ge: greater than or equal
>> le: less than or equal
>>
>> ??
>>
>>
>>
>> On Fri, Jan 1, 2016 at 2:25 PM, William Bell  wrote:
>>
>>> This all started with me trying to use {!switch} to indicate with CO or
>>> NY to use. if we pass state1, that is supposed to take precedence, but if
>>> nothing is returned, then use state Make sense now?
>>>
>>> I could not find a way to check for strlen($state1). Which is what I
>>> want in the case statement. This just does not work...
>>> Something like the following is what I am trying to do:
>>>
>>>
>>> fq={!switch case."anything"=$state1
>>> default=$state
>>>  v=$state1}
>>>
>>> So I tried the following to set all 50 states:
>>>
>>>
>>> fq={!switch case.all='*:*'
>>>  case.CO='state:CO'
>>>  case.NY='state:NY'
>>>  v=$state1}
>>>
>>>
>>> Obviously Oregon (OR!) is an issue, and it won't work at all plus
>>>
>>>
>>>
>>> On Fri, Jan 1, 2016 at 2:15 PM, William Bell 
>>> wrote:
>>>
>>>> Another weirdness:
>>>>
>>>>
>>>> http://localhost:8983/solr/providersearch/select?wt=json&state=state:CO&state1=state:NY&fl=*&q=*:*&tt=$state1&fq={!lucene%20v=$tt}
>>>> <http://localhost:8983/solr/providersearch/select?wt=json&state=state:CO&state1=state:NY&fl=*&q=*:*&tt=$state1&fq=%7B!lucene%20v=$tt%7D>
>>>>
>>>> That does not return anything.
>>>>
>>>> But if I set v=$state1 I get results.
>>>>
>>>> Can I not set equivalent variables?
>>>>
>>>>
>>>>
>>>> On Fri, Jan 1, 2016 at 2:07 PM, William Bell 
>>>> wrote:
>>>>
>>>>> Example.
>>>>>
>>>>>
>>>>> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state1}
>>>>> <http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq=%7B!lucene%20v=$state1%7D>
>>>>>
>>>>> This return 236,000
>>>>>
>>>>>
>>>>> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state}
>>>>> <http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq=%7B!lucene%20v=$state%7D>
>>>>>
>>>>> This returns 10,000
>>>>>
>>>>> I want to put an IF statement around which v to use.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Jan 1, 2016 at 1:52 PM, William Bell 
>>>>> wrote:
>>>>>
>>>>>> Sure.
>>>>>>
>>>>>> If the state:NY returns results filter by state:NY, if it does not,
>>>>>> then use state:CO. If we have results in NY, use it, otherwise use CO.
>>>>>>
>>>>>> OK?
>>>>>>
>>>>>> On Fri, Jan 1, 2016 at 1:15 PM, Upayavira  wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Dec 31, 2015, at 11:50 PM, William Bell wrote:
>>>>>>> > We are getting weird results with if(exists(a),b,c). We are
>>>>>>> getting b+c!!
>>>>>>> >
>>>>&g

Re: Issue with if() statement

[William Bell]

Sample code for a simple query parser?

On Fri, Jan 1, 2016 at 3:08 PM, Upayavira  wrote:

> You've got to think of what the queries will be that you produce under
> the bonnet - what you are talking about is either a (!func} or a
> {!frange} query - both of which are inefficient as they must scan the
> entire resultset.
>
> However, what you're trying to do is evaluate the length of the *input
> value*, not a value in the documents being searched, so this doesn't
> really apply - you're talking about doing some work before your query
> happens.
>
> Again, I'm not sure of a way to do this on a stock Solr, but with a
> little coding it should be achievable - you could extend the switch
> query parser, or you could write your own - they're not that hard to
> create. Or, you could create a search component that operates before the
> QueryComponent does.
>
> A simple queryparser of your own would seem like a pretty lightweight
> thing - probably 20 lines of code or less.
>
> Upayavira
>
> On Fri, Jan 1, 2016, at 09:40 PM, William Bell wrote:
> > Forgot last bit:
> >
> > fq={!switch case.gt.0=$state1
> >      default=$state
> >  func=len($state1)}
> >
> >
> > On Fri, Jan 1, 2016 at 2:39 PM, William Bell 
> wrote:
> >
> > > Maybe we can add function value on a switch?
> > >
> > > fq={!switch case.gt.0
> > >  default=$state
> > >  func=len($state1)}
> > >
> > >
> > >
> > > We could add: gt, lt, eq, ge, le ?
> > >
> > > gt: greater than
> > > lt: less than
> > > eq: equal
> > > ge: greater than or equal
> > > le: less than or equal
> > >
> > > ??
> > >
> > >
> > >
> > > On Fri, Jan 1, 2016 at 2:25 PM, William Bell 
> wrote:
> > >
> > >> This all started with me trying to use {!switch} to indicate with CO
> or
> > >> NY to use. if we pass state1, that is supposed to take precedence,
> but if
> > >> nothing is returned, then use state Make sense now?
> > >>
> > >> I could not find a way to check for strlen($state1). Which is what I
> want
> > >> in the case statement. This just does not work...
> > >> Something like the following is what I am trying to do:
> > >>
> > >>
> > >> fq={!switch case."anything"=$state1
> > >>     default=$state
> > >>  v=$state1}
> > >>
> > >> So I tried the following to set all 50 states:
> > >>
> > >>
> > >> fq={!switch case.all='*:*'
> > >>  case.CO='state:CO'
> > >>  case.NY='state:NY'
> > >>  v=$state1}
> > >>
> > >>
> > >> Obviously Oregon (OR!) is an issue, and it won't work at all plus
> > >>
> > >>
> > >>
> > >> On Fri, Jan 1, 2016 at 2:15 PM, William Bell 
> wrote:
> > >>
> > >>> Another weirdness:
> > >>>
> > >>>
> > >>>
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:CO&state1=state:NY&fl=*&q=*:*&tt=$state1&fq={!lucene%20v=$tt}
> > >>> <
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:CO&state1=state:NY&fl=*&q=*:*&tt=$state1&fq=%7B!lucene%20v=$tt%7D
> >
> > >>>
> > >>> That does not return anything.
> > >>>
> > >>> But if I set v=$state1 I get results.
> > >>>
> > >>> Can I not set equivalent variables?
> > >>>
> > >>>
> > >>>
> > >>> On Fri, Jan 1, 2016 at 2:07 PM, William Bell 
> > >>> wrote:
> > >>>
> > >>>> Example.
> > >>>>
> > >>>>
> > >>>>
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state1}
> > >>>> <
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq=%7B!lucene%20v=$state1%7D
> >
> > >>>>
> > >>&g

Re: Add support in FacetsComponent for facet.method=uif

[William Bell]

Yes we would like backward compatibility. We cannot switch all the facet
fields to DocValues and our faceting is slow.

Please...

On Fri, Jan 1, 2016 at 7:41 AM, Jamie Johnson  wrote:

> Is there any interest in this?  While i think it's important and inline
> with faceting available in the new json facet api, I've seen no discussion
> on it so I'm wondering if it's best I add support for this using a custom
> facet component even though the majority of the component will be a copy
> which is prefer to not need to maintain separately.
>
> Jamie
> On Dec 22, 2015 12:37 PM, "Jamie Johnson"  wrote:
>
> > I had previously piggybacked on another post, but I think it may have
> been
> > lost there.  I had a need to do UnInvertedField based faceting in the
> > FacetsComponent and as such started looking at what would be required to
> > implement something similar to what the JSON Facets based API does in
> this
> > regard.  The patch that I have in this regard works and is attached to
> > https://issues.apache.org/jira/browse/SOLR-8096, is that appropriate or
> > should I create a new ticket to specifically add this support?
> >
> > -Jamie
> >
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Issue with if() statement

[William Bell]

OK. I was able to get it to work by looking at {!switch} code. I had a heck
of a time trying to get parse() to work as a separate class.

q.add(new TermQuery(new Term("state", "CO"), Occur.MUST);
return q;

That never did anything.

Here is some code that worked...

http://localhost:8983/solr/providersearchfull/select?wt=json&state1=state:NY&fl=ss,score&df=state&q={!orquery}$state,$state1

Notice $state was not sent... It works.

Thoughts?

package hg.parsers;

import org.apache.commons.lang.StringUtils;
import org.apache.lucene.index.Term;
import org.apache.lucene.search.BooleanClause.Occur;
import org.apache.lucene.search.BooleanQuery;
import org.apache.solr.common.params.CommonParams;
import org.apache.lucene.search.TermQuery;
import org.apache.lucene.search.BooleanClause;
import org.apache.solr.parser.QueryParser;
import org.apache.lucene.search.Query;
import org.apache.lucene.search.spans.SpanTermQuery;
import org.apache.solr.common.params.SolrParams;
import org.apache.solr.search.QueryParsing;
import org.apache.solr.common.util.NamedList;
import org.apache.solr.request.SolrQueryRequest;
import org.apache.solr.search.QParser;
import org.apache.solr.search.QParserPlugin;
import org.apache.solr.search.SyntaxError;

/**
 * Created by bbell on 1/3/16.
 */
public class OrQueryParserPlugin extends QParserPlugin {
//public static String NAME = "lucene";

@Override
public void init(NamedList args) {
}

@Override
public QParser createParser(String qstr, SolrParams localParams,
SolrParams params, SolrQueryRequest req) {
return new QParser(qstr, localParams, params, req) {
QParser subParser;

@Override
public Query parse() throws SyntaxError {
String v = localParams.get(QueryParsing.V);
if (v == null || v.length() == 0) return null;
String subQ = null;

String[] arr = v.split(",");
System.out.println("parse arr:" + arr.length + "," + v);
if (arr != null && arr.length == 2) {
System.out.println("parse arr[0].length:" +
arr[0].length());
System.out.println("parse arr[1].length:" +
arr[1].length());
if (arr[0].trim().length() > 0) {
System.out.println("parse arr[0] params:" +
params.get(arr[0].trim()));
if (arr[0].trim().substring(0, 1).equals("$")) {
String val = params.get(arr[0].trim().substring(1));
if (val != null && val.length() > 0) {
subQ = val;
System.out.println("parse arr[0]:" +
arr[0].trim() + "," + subQ);
}
} else {
subQ = arr[0].trim();
System.out.println("parse arr[0]:" + subQ);
}
}
if (subQ == null && arr[1].trim().length() > 0) {
System.out.println("parse arr[1] params:" +
params.get(arr[1].trim()));
if (arr[1].trim().substring(0, 1).equals("$")) {
String val = params.get(arr[1].trim().substring(1));
if (val != null && val.length() > 0) {
subQ = val;
System.out.println("parse arr[1]:" +
arr[1].trim() + "," + subQ);
}
} else {
subQ = arr[1].trim();
System.out.println("parse arr[1]:" + subQ);
}
}
} else {
subQ = null;
}

subParser = subQuery(subQ, null);
return subParser.getQuery();
}
@Override
public String[] getDefaultHighlightFields() {
return subParser.getDefaultHighlightFields();
}

@Override
public Query getHighlightQuery() throws SyntaxError {
return subParser.getHighlightQuery();
}

@Override
public void addDebugInfo(NamedList debugInfo) {
subParser.addDebugInfo(debugInfo);
}
};
}
}



.

On Sat, Jan 2, 2016 at 5:03 AM, Upayavira  wrote:

> Hrmph. I've got an Ant based codebase for building custom components
> against Solr. I've been asked on numerous occasions to publish this
> codebase. It is now at:
>
> https://github.com/upayavira/custom-solr-components
>
> There's no sample code i

Re: Issue with if() statement

[William Bell]

Thanks that indeed works tt=${state1}. But that was just a passing question.

I see an empty "*case*", "default" and a "case.VAL". I think I have
anything I need. After rereading. We might want to add to "case.VAL"
something like "case.'state:CO'" with a single quote. Right now it does not
appear to handle spaces or : I digress.

I got it to work with {!switch}.

http://localhost:8983/solr/providersearchfull/select?wt=xml&state1=state:%22NY%22&fl=score&q=*:*&fq={!switch%20case=$state2%20default=$state1%20v=$state1}

If the user passes state1, it will not be empty and the default will pick
up all 50 states.

If the user does not pass state1, but passes state2, the case empty will
pick up since $state1 is empty, and it works.

http://localhost:8983/solr/providersearchfull/select?wt=xml&state2=state:%22CO%22&fl=score&q=*:*&fq={!switch%20case=$state2%20default=$state1%20v=$state1}

The only that that changes is if I set as a param state1 or state2.

If I send both state1 and state2, state1 takes precedence.

http://localhost:8983/solr/providersearchfull/select?wt=xml&state1=state:%22NY%22&state2=state:%22CO%22&fl=score&q=*:*&fq={!switch%20case=$state2%20default=$state1%20v=$state1}

Kinda interesting.

The query I sent earlier : {!orquery}query1,query2 will return query1 is it
is not empty, otherwise if query1 is empty it will run query2. That was the
code I sent last night.

I am going to send some more code, since I could not get TermQuery to work
like I have it in PayLoad. And need some help debugging that.

Thanks!



On Sun, Jan 3, 2016 at 11:32 AM, Erik Hatcher 
wrote:

> I haven’t fully digested this thread, but wanted to comment on this one.
> ¶m=$something doesn’t substitute.  Only “local” params (inside local
> param syntax curly brackets) do that.  If you want to substitute a raw
> parameter use curly brackets.  You could, in this example, use
> &tt=${state1}, I believe, and it would substitute.  Confusingly, local
> param curly brackets are _not_ the same as param substitution curly
> brackets.
>
> I am skeptical that anything custom is needed for what you’re trying to
> do, but again I haven’t fully digested what’s going on here yet.  There is
> some param substitution and {!switch} voodoo in example/files that ships
> with Solr, and that might be helpful.  Check out how that works.  I’m in
> the polishing stages of a a collaborative blog post on example/files that
> will detail these tricks a bit - will publish that in the next few days.
>
> —
> Erik Hatcher, Senior Solutions Architect
> http://www.lucidworks.com <http://www.lucidworks.com/>
>
>
>
> > On Jan 1, 2016, at 4:15 PM, William Bell  wrote:
> >
> > Another weirdness:
> >
> >
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:CO&state1=state:NY&fl=*&q=*:*&tt=$state1&fq={!lucene%20v=$tt}
> >
> > That does not return anything.
> >
> > But if I set v=$state1 I get results.
> >
> > Can I not set equivalent variables?
> >
> >
> >
> > On Fri, Jan 1, 2016 at 2:07 PM, William Bell 
> wrote:
> >
> >> Example.
> >>
> >>
> >>
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state1}
> >> <
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq=%7B!lucene%20v=$state1%7D
> >
> >>
> >> This return 236,000
> >>
> >>
> >>
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state}
> >> <
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq=%7B!lucene%20v=$state%7D
> >
> >>
> >> This returns 10,000
> >>
> >> I want to put an IF statement around which v to use.
> >>
> >>
> >>
> >>
> >>
> >>
> >> On Fri, Jan 1, 2016 at 1:52 PM, William Bell 
> wrote:
> >>
> >>> Sure.
> >>>
> >>> If the state:NY returns results filter by state:NY, if it does not,
> then
> >>> use state:CO. If we have results in NY, use it, otherwise use CO.
> >>>
> >>> OK?
> >>>
> >>> On Fri, Jan 1, 2016 at 1:15 PM, Upayavira  wrote:
> >>>
> >>>>
> >>>>
> >>>> On Thu, Dec 31, 2015, at 11:50

Re: Add support in FacetsComponent for facet.method=uif

[William Bell]

Interesting that facet.method=dv or facet.method=uif. What is the
difference?

On Sun, Jan 3, 2016 at 6:44 AM, Jamie Johnson  wrote:

> For those interested I created a separate jira issue for this but forgot to
> attach earlier.
>
> https://issues.apache.org/jira/browse/SOLR-8466
> On Jan 2, 2016 8:45 PM, "William Bell"  wrote:
>
> > Yes we would like backward compatibility. We cannot switch all the facet
> > fields to DocValues and our faceting is slow.
> >
> > Please...
> >
> > On Fri, Jan 1, 2016 at 7:41 AM, Jamie Johnson  wrote:
> >
> > > Is there any interest in this?  While i think it's important and inline
> > > with faceting available in the new json facet api, I've seen no
> > discussion
> > > on it so I'm wondering if it's best I add support for this using a
> custom
> > > facet component even though the majority of the component will be a
> copy
> > > which is prefer to not need to maintain separately.
> > >
> > > Jamie
> > > On Dec 22, 2015 12:37 PM, "Jamie Johnson"  wrote:
> > >
> > > > I had previously piggybacked on another post, but I think it may have
> > > been
> > > > lost there.  I had a need to do UnInvertedField based faceting in the
> > > > FacetsComponent and as such started looking at what would be required
> > to
> > > > implement something similar to what the JSON Facets based API does in
> > > this
> > > > regard.  The patch that I have in this regard works and is attached
> to
> > > > https://issues.apache.org/jira/browse/SOLR-8096, is that appropriate
> > or
> > > > should I create a new ticket to specifically add this support?
> > > >
> > > > -Jamie
> > > >
> > >
> >
> >
> >
> > --
> > Bill Bell
> > billnb...@gmail.com
> > cell 720-256-8076
> >
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Add support in FacetsComponent for facet.method=uif

[William Bell]

Ok the path appears to have dv and uif in there.?

On Sun, Jan 3, 2016 at 4:40 PM, Jamie Johnson  wrote:

> The patch adds facet.method=uif and then delegates all of the work to the
> JSON Faceting API to do the work.  I had originally added a facet.method=dv
> and made the original facet.method=fc work using the UnInvertedField but
> wanted to avoid making a change that would introduce unexpected behavior.
> While I think it's strange that facet.method=dv does not exist and fc
> defaults to dv I think if we wanted to change that it should be done in
> another ticket.
>
> On Sun, Jan 3, 2016 at 4:18 PM, William Bell  wrote:
>
> > Interesting that facet.method=dv or facet.method=uif. What is the
> > difference?
> >
> > On Sun, Jan 3, 2016 at 6:44 AM, Jamie Johnson  wrote:
> >
> > > For those interested I created a separate jira issue for this but
> forgot
> > to
> > > attach earlier.
> > >
> > > https://issues.apache.org/jira/browse/SOLR-8466
> > > On Jan 2, 2016 8:45 PM, "William Bell"  wrote:
> > >
> > > > Yes we would like backward compatibility. We cannot switch all the
> > facet
> > > > fields to DocValues and our faceting is slow.
> > > >
> > > > Please...
> > > >
> > > > On Fri, Jan 1, 2016 at 7:41 AM, Jamie Johnson 
> > wrote:
> > > >
> > > > > Is there any interest in this?  While i think it's important and
> > inline
> > > > > with faceting available in the new json facet api, I've seen no
> > > > discussion
> > > > > on it so I'm wondering if it's best I add support for this using a
> > > custom
> > > > > facet component even though the majority of the component will be a
> > > copy
> > > > > which is prefer to not need to maintain separately.
> > > > >
> > > > > Jamie
> > > > > On Dec 22, 2015 12:37 PM, "Jamie Johnson" 
> wrote:
> > > > >
> > > > > > I had previously piggybacked on another post, but I think it may
> > have
> > > > > been
> > > > > > lost there.  I had a need to do UnInvertedField based faceting in
> > the
> > > > > > FacetsComponent and as such started looking at what would be
> > required
> > > > to
> > > > > > implement something similar to what the JSON Facets based API
> does
> > in
> > > > > this
> > > > > > regard.  The patch that I have in this regard works and is
> attached
> > > to
> > > > > > https://issues.apache.org/jira/browse/SOLR-8096, is that
> > appropriate
> > > > or
> > > > > > should I create a new ticket to specifically add this support?
> > > > > >
> > > > > > -Jamie
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Bill Bell
> > > > billnb...@gmail.com
> > > > cell 720-256-8076
> > > >
> > >
> >
> >
> >
> > --
> > Bill Bell
> > billnb...@gmail.com
> > cell 720-256-8076
> >
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Issue with Join

[William Bell]

Can a committer take a look at this please?


On Wed, Dec 30, 2015 at 4:35 PM, William Bell  wrote:

> Yeah I ran it. It appears to only have an issue if the field for the core
> on the outside is MultiValue, and the inside field is single value, and the
> order of the field has the code not as the first entry. Like:
>
>  practicing_specialties_codes:
> >  [
> > - "PS1010",
> > - "PS282",
> > - "*PS1226*"
> > ]
> >  }
>
> Here is the output of the debug:
>
>
>- join:
>{
>   - {!join from=prac_spec_code to=practicing_specialties_codes
>   fromIndex=autosuggest}*:*:
>   {
>  - time: 24,
>  - fromSetSize: 170179,
>  - toSetSize: 3194542,
>  - fromTermCount: 1091,
>  - fromTermTotalDf: 1091,
>  - fromTermDirectCount: 1091,
>  - fromTermHits: 1091,
>  - fromTermHitsTotalDf: 1091,
>  - toTermHits: 1069,
>  - toTermHitsTotalDf: 4002538,
>  - toTermDirectCount: 697,
>  - smallSetsDeferred: 1,
>  - toSetDocsAdded: 4002538
>  }
>   },
>
>
> On Wed, Dec 30, 2015 at 2:02 AM, Mikhail Khludnev <
> mkhlud...@griddynamics.com> wrote:
>
>> Hello,
>>
>> Have you considered to pass NOT {!join from=prac_spec_code
>> to=practicing_specialties_codes
>>  fromIndex=autosuggest}*:* as a q and look at debug output.
>> Also there was a trick for dealing with pure negative queries q=*:*
>> -foo:bar though it might be obsolete.
>>
>> On Tue, Dec 29, 2015 at 7:02 AM, William Bell 
>> wrote:
>>
>> > I have having issues with {!join}. If the core have multiValued field
>> and
>> > the inner join does not have a multiValued field it does not find the
>> > ones...
>> >
>> > Solr 5.3.1... 5.3.1
>> >
>> > Example.
>> >
>> > PS1226 is in practicing_specialties_codes in providersearch core. This
>> > field is multiValued.
>> >
>> > in the autosuggest core there is NOT a field for PS1226 in there. This
>> > field is called prac_spec_code and is single values.
>> >
>> >
>> >
>> >
>> http://localhost:8983/solr/providersearch/select?q=*%3A*&wt=json&indent=true&fq=practicing_specialties_codes:PS1226&fl=practicing_specialties_codes
>> >
>> > I get:
>> >
>> >
>> >- docs:
>> >[
>> >   -
>> >   {
>> >  - practicing_specialties_codes:
>> >  [
>> > - "PS1010",
>> > - "PS282",
>> > - "PS1226"
>> > ]
>> >  }
>> >   ]
>> >
>> >
>> >
>> > In autosuggest there is nothing:
>> >
>> >
>> >
>> http://localhost:8983/solr/autosuggest/select?q=*%3A*&wt=json&indent=true&fq=prac_spec_code:PS1226&fl=prac_spec_code
>> >
>> > Nothing.
>> >
>> > Then a join should find what is in providersearch but missing in
>> > autosuggest.
>> >
>> >
>> >
>> http://localhost:8983/solr/providersearch/select?debugQuery=true&wt=json&q=*:*&rows=10&fq=practicing_specialties_codes:PS1226&fl=practicing_specialties_codes&fq=NOT%20{!join%20from=prac_spec_code%20to=practicing_specialties_codes%20fromIndex=autosuggest}auto_type:PRACSPEC
>> <http://localhost:8983/solr/providersearch/select?debugQuery=true&wt=json&q=*:*&rows=10&fq=practicing_specialties_codes:PS1226&fl=practicing_specialties_codes&fq=NOT%20%7B!join%20from=prac_spec_code%20to=practicing_specialties_codes%20fromIndex=autosuggest%7Dauto_type:PRACSPEC>
>> >
>> > or
>> >
>> >
>> >
>> http://hgsolr2sl1:8983/solr/providersearch/select?debugQuery=true&wt=json&q=*:*&rows=10&fl=practicing_specialties_codes&fq=NOT%20{!join%20from=prac_spec_code%20to=practicing_specialties_codes%20fromIndex=autosuggest}auto_type:PRACSPEC
>> <http://hgsolr2sl1:8983/solr/providersearch/select?debugQuery=true&wt=json&q=*:*&rows=10&fl=practicing_specialties_codes&fq=NOT%20%7B!join%20from=prac_spec_code%20to=practicing_specialties_codes%20fromIndex=autosuggest%7Dauto_type:PRACSPEC>
>> >
>> > or
>> >
>> >
>> >
>> http://hgsolr2sl1:8983/solr/providersearch/select?debugQuery=true&wt=json&q=*:*&rows=10&fl

What search metrics are useful?

[William Bell]

How do others look at search metrics?

1. Search conversion? Do you look at searches and if the user does not
click on a result, and reruns the search that would be a failure?

2. How to measure auto complete success metrics?

3. Facets/filters could be considered negative, since we did not find the
results that the user wanted, and now they are filtering - who to measure?

4. One easy metric is searches with 0 results. We could auto expand the geo
distance or ask the user "did you mean" ?

5. Another easy one would be tech performance: "time it takes in seconds to
get a result".

6. How to measure fuzzy? How do you know you need more synonyms? How to
measure?

7. How many searches it takes before the user clicks on a result?

Other ideas? Is there a video or presentation on search metrics that would
be useful?

-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

XX:ParGCCardsPerStrideChunk

[William Bell]

Has anyone tried -XX:ParGCCardsPerStrideChunk with Solr?

There has been reports of improved GC times.

-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Field exclusion from fl and hl.fl

[William Bell]

it used to support

fl=*,-field

Does that not work now?

On Sat, Mar 5, 2016 at 7:37 PM, Zheng Lin Edwin Yeo 
wrote:

> I have yet to find any workaround so far.Still have to list out all the
> remaining fields one by one.
>
> Does anyone else has any suggestions?
>
> Regards,
> Edwin
>
>
> On 18 February 2016 at 17:07, Anil  wrote:
>
> > I am looking for the same. please do let me know just in case you find
> > workaround.
> >
> > On 18 February 2016 at 14:18, Zheng Lin Edwin Yeo 
> > wrote:
> >
> > > Hi,
> > >
> > > Would like to find out, is there already a way to exclude field from
> the
> > > Solr response. I did came across SOLR-3191 which was created about 4
> > years
> > > ago, but could not find any workable solutions from there.
> > >
> > > As my collections can have more than 100 fields, and I would need to
> > return
> > > the majority of then except for one or two, so if there is a way to
> > exclude
> > > the fields would be good, if not I have to list all the remaining
> fields
> > > (which can be more than 100 for each collections).
> > >
> > > I am using Solr 5.4.0.
> > >
> > > Regards,
> > > Edwin
> > >
> >
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Field exclusion from fl and hl.fl

[William Bell]

Can we get this over the goal line?

https://issues.apache.org/jira/browse/SOLR-3191

On Sun, Mar 6, 2016 at 3:16 AM, Zheng Lin Edwin Yeo 
wrote:

> Hi,
>
> No, I tried that and I got the following error.
>
> {
>   "responseHeader":{
> "status":500,
> "QTime":0},
>   "error":{
> "msg":"For input string: \"-\"",
> "trace":"java.lang.NumberFormatException: For input string:
> \"-\"\r\n\tat
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)\r\n\tat
> java.lang.Long.parseLong(Long.java:581)\r\n\tat
> java.lang.Long.parseLong(Long.java:631)\r\n\tat
> org.apache.solr.search.StrParser.getNumber(StrParser.java:124)\r\n\tat
>
> org.apache.solr.search.FunctionQParser.parseValueSource(FunctionQParser.java:298)\r\n\tat
>
> org.apache.solr.search.FunctionQParser.parse(FunctionQParser.java:80)\r\n\tat
> org.apache.solr.search.QParser.getQuery(QParser.java:141)\r\n\tat
>
> org.apache.solr.search.SolrReturnFields.add(SolrReturnFields.java:297)\r\n\tat
>
> org.apache.solr.search.SolrReturnFields.parseFieldList(SolrReturnFields.java:113)\r\n\tat
>
> org.apache.solr.search.SolrReturnFields.(SolrReturnFields.java:99)\r\n\tat
>
> org.apache.solr.search.SolrReturnFields.(SolrReturnFields.java:75)\r\n\tat
>
> org.apache.solr.handler.component.QueryComponent.prepare(QueryComponent.java:139)\r\n\tat
>
> org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:247)\r\n\tat
>
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:156)\r\n\tat
> org.apache.solr.core.SolrCore.execute(SolrCore.java:2073)\r\n\tat
> org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:658)\r\n\tat
> org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:457)\r\n\tat
>
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:222)\r\n\tat
>
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:181)\r\n\tat
>
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)\r\n\tat
>
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)\r\n\tat
>
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)\r\n\tat
>
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)\r\n\tat
>
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)\r\n\tat
>
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)\r\n\tat
>
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)\r\n\tat
>
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)\r\n\tat
>
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)\r\n\tat
>
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)\r\n\tat
>
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)\r\n\tat
>
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110)\r\n\tat
>
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)\r\n\tat
> org.eclipse.jetty.server.Server.handle(Server.java:499)\r\n\tat
> org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)\r\n\tat
>
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)\r\n\tat
>
> org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)\r\n\tat
>
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)\r\n\tat
>
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)\r\n\tat
> java.lang.Thread.run(Thread.java:745)\r\n",
> "code":500}}
>
>
> Regards,
> Edwin
>
>
> On 6 March 2016 at 11:19, William Bell  wrote:
>
> > it used to support
> >
> > fl=*,-field
> >
> > Does that not work now?
> >
> > On Sat, Mar 5, 2016 at 7:37 PM, Zheng Lin Edwin Yeo <
> edwinye...@gmail.com>
> > wrote:
> >
> > > I have yet to find any workaround so far.Still have to list out all the
> > > remaining fields one by one.
> > >
> > > Does anyone else has any suggestions?
> > >
> > > Regards,
> > > Edwin
> > >
> > >
> > > On 18 February 2016 at 17:07, Anil  wrote:
> > >
> > > > I am looking for the same. please do let me know just in case you
> find
> > > > workaround.
> > > >
> > > > On 18 February 2016 at 14:18, Zheng Lin Ed

Re: DIG issue with SolrEntityProcessor 5.4.1

[William Bell]

I will try to see if I can create a use case and fix it.

On Wed, Mar 16, 2016 at 10:00 AM, William Bell  wrote:

> We are running this inside of another entity in DIH. There appears to be
> an issue. We get 2 calls to the survey core if hits > 0. If hits = 0 we get
> 1 call. Has anyone else seen this? Shall I fix it? Any ideas where this bug
> may be?
>
> http://localhost:8983/solr/survey"; qt="dihsurvey" query="provider_code:${
> item.id}" rows="1">   entity>
>
>
> 2016-03-16 09:57:11.349 INFO  (qtp796684896-71) [   x:survey]
> o.a.s.c.S.Request [survey] webapp=/solr path=/select
> params={q=provider_code:X4L26&qt=dihsurvey&start=0&timeAllowed=30&rows=1&wt=javabin&version=2}
> hits=0 status=0 QTime=1
>
> 2016-03-16 09:57:11.398 INFO  (qtp796684896-23) [   x:survey]
> o.a.s.c.S.Request [survey] webapp=/solr path=/select
> params={q=provider_code:2J8CP&qt=dihsurvey&start=0&timeAllowed=30&rows=1&wt=javabin&version=2}
> hits=427 status=0 QTime=2
>
> 2016-03-16 09:57:11.402 INFO  (qtp796684896-173) [   x:survey]
> o.a.s.c.S.Request [survey] webapp=/solr path=/select
> params={q=provider_code:2J8CP&qt=dihsurvey&start=1&timeAllowed=30&rows=1&wt=javabin&version=2}
> hits=427 status=0 QTime=1
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 720-256-8076
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

DIG issue with SolrEntityProcessor 5.4.1

[William Bell]

We are running this inside of another entity in DIH. There appears to be an
issue. We get 2 calls to the survey core if hits > 0. If hits = 0 we get 1
call. Has anyone else seen this? Shall I fix it? Any ideas where this bug
may be?

http://localhost:8983/solr/survey"; qt="dihsurvey" query="provider_code:${
item.id}" rows="1">  


2016-03-16 09:57:11.349 INFO  (qtp796684896-71) [   x:survey]
o.a.s.c.S.Request [survey] webapp=/solr path=/select
params={q=provider_code:X4L26&qt=dihsurvey&start=0&timeAllowed=30&rows=1&wt=javabin&version=2}
hits=0 status=0 QTime=1

2016-03-16 09:57:11.398 INFO  (qtp796684896-23) [   x:survey]
o.a.s.c.S.Request [survey] webapp=/solr path=/select
params={q=provider_code:2J8CP&qt=dihsurvey&start=0&timeAllowed=30&rows=1&wt=javabin&version=2}
hits=427 status=0 QTime=2

2016-03-16 09:57:11.402 INFO  (qtp796684896-173) [   x:survey]
o.a.s.c.S.Request [survey] webapp=/solr path=/select
params={q=provider_code:2J8CP&qt=dihsurvey&start=1&timeAllowed=30&rows=1&wt=javabin&version=2}
hits=427 status=0 QTime=1

-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Example Transformer

[William Bell]

I wrote a transformer for DIH to get the value from a field using Http call.
Since this runs on a SOLR node when indexing, I think I would do it with
SOLRJ.

How do I take this and convert it to SOLRJ and avoid the network call ?

Also, this is pretty cool, and avoids the Entity for the call - since using
an Entity has issues which I reported on a few days ago. It is much easier
to access all fields when using a transformer.

http://localhost:8983/solr/survey/select";
qt="dihsurvey" source="provider_json" />

package hg;

import net.sf.json.JSON;
import net.sf.json.JSONObject;
import net.sf.json.JSONArray;
import java.io.BufferedReader;
import java.io.IOException;
import java.io.InputStream;
import java.io.InputStreamReader;
import java.io.Reader;
import java.net.URL;
import java.net.URLConnection;
import java.nio.charset.Charset;

import java.io.IOException;
import org.apache.solr.handler.dataimport.Context;
import org.apache.solr.handler.dataimport.DataImporter;
import org.apache.solr.handler.dataimport.Transformer;

import java.util.List;
import java.util.Map;


// Overwrite for Survey embedded entity
// http://localhost:8983/solr/survey/select"; qt="dihsurvey"
source="provider_json" />

public class JSONProviderSurvey extends Transformer {

private static String readAll(Reader rd) throws IOException {
StringBuilder sb = new StringBuilder();
int cp;
while ((cp = rd.read()) != -1) {
sb.append((char) cp);
}
return sb.toString();
}

public static JSONObject readJsonFromUrl(String urlPath) throws
IOException {
URL url = new URL(urlPath);
URLConnection con = url.openConnection();
con.setConnectTimeout(1);
con.setReadTimeout(1);
InputStream is = con.getInputStream();
//InputStream is = new URL(url).openStream();
try {
BufferedReader rd = new BufferedReader(new
InputStreamReader(is, Charset.forName("UTF-8")));
String jsonText = readAll(rd);
JSONObject json = JSONObject.fromObject(jsonText);
return json;
} finally {
is.close();
}
}

public Map transformRow(Map row,
Context context) {

List> fields = context.getAllEntityFields();

for (Map field : fields) {
String jsonf = field.get("jsonprovidersurvey");

if ("true".equals(jsonf)) {

String columnName = field.get(DataImporter.COLUMN);
String url = field.get("url");
//url = "http://hgsolr2devmstr:8983/solr/survey/select";;
String qt = field.get("qt");
//qt = "dihsurvey";
String pwid = SolrUtility.GetSafeString(row.get("id"));
String source = field.get("source");
String outfield =
SolrUtility.GetSafeString(field.get("outfield"));
if (row.get(source) != null) {

Object jobject = row.get(source);
JSONObject provider =
JSONObject.fromObject(jobject.toString());
JSONObject json;
try {
json = readJsonFromUrl(url + "?qt=" + qt +
"&q=provider_code:" + pwid.toUpperCase() +
"&wt=json&rows=1&omitHeader=true");
if (json.get("response") != null) {
JSONObject response =
json.getJSONObject("response");
JSONArray docs = response.getJSONArray("docs");
if (docs.size() > 0) {
JSONObject doc = docs.getJSONObject(0);
boolean has_comment =
SolrUtility.GetSafeBool(doc.get("has_comment"));
provider.element("HasOpenComment", has_comment);
row.put(columnName, provider.toString());
if (outfield.length() > 0) {
row.put(outfield, has_comment);
}
}
}
} catch (Exception e) {
provider.element("HasOpenComment", false);
row.put(columnName, provider.toString());
if (outfield.length() > 0) {
row.put(outfield, false);
}
}
}
}
}

return row;
}
}



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

issue with 5.3.1 and index version

[William Bell]

When I index 5.4.1 using luceneVer in solrlconfig.xml of 5.3.1, the
segmentsw_9 files has in it Lucene54. Why? Is this a known bug?

#strings segments_9

segments

Lucene54

commitTimeMSec

1459374733276




-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: issue with 5.3.1 and index version

[William Bell]

What we are trying to do is - we upgraded the Solr Master machine to 5.4.1,
and the slave is 5.3.1. When it replicates to the slave, it says
"incompatible types". That seems like a valid use case to me?

BIll


On Thu, Mar 31, 2016 at 2:49 AM, Shalin Shekhar Mangar <
shalinman...@gmail.com> wrote:

> The Lucene54 is the codec name. The luceneVer in solrconfig.xml is the
> compatibility version which is used by some analyzers/tokenizers/token
> filters to provide defaults or behaviour compatible with older versions. It
> has no relation to the indexing codec being used and once an index has been
> written to by a newer version of Lucene, going back to an old version is
> not possible in most cases.
>
> On Thu, Mar 31, 2016 at 4:00 AM, William Bell  wrote:
>
> > When I index 5.4.1 using luceneVer in solrlconfig.xml of 5.3.1, the
> > segmentsw_9 files has in it Lucene54. Why? Is this a known bug?
> >
> > #strings segments_9
> >
> > segments
> >
> > Lucene54
> >
> > commitTimeMSec
> >
> > 1459374733276
> >
> >
> >
> >
> > --
> > Bill Bell
> > billnb...@gmail.com
> > cell 720-256-8076
> >
>
>
>
> --
> Regards,
> Shalin Shekhar Mangar.
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Unexpected docvalues type error using result grouping - Use UninvertingReader or index with docvalues

[William Bell]

You could try stopping SOLR, going into the data directory and rm -rf * and
starting SOLR again.

Did you use the schema REST api? Residual ?

On Thu, Jul 23, 2015 at 6:57 PM, Shamik Bandopadhyay 
wrote:

> Hi,
>
>  I'm facing this weird error while running result grouping queries. This
> started when I turned on "docvalues" for an existing facet field and
> indexed the documents. Looking at the exception, I reverted back the change
> and re-indexed the documents again. But I'm still getting the exception,
> here's the stack trace.
>
> ERROR SolrCore org.apache.solr.common.SolrException: Exception during
> facet.field: MediaType
>
> org.apache.solr.common.SolrException: Exception during facet.field:
> MediaType
> at
> org.apache.solr.request.SimpleFacets$3.call(SimpleFacets.java:596)
> at
> org.apache.solr.request.SimpleFacets$3.call(SimpleFacets.java:581)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.apache.solr.request.SimpleFacets$2.execute(SimpleFacets.java:535)
> at
> org.apache.solr.request.SimpleFacets.getFacetFieldCounts(SimpleFacets.java:606)
> at
> org.apache.solr.request.SimpleFacets.getFacetCounts(SimpleFacets.java:258)
> at
> org.apache.solr.handler.component.FacetComponent.process(FacetComponent.java:107)
> at
> org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:227)
> at
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:144)
> at org.apache.solr.core.SolrCore.execute(SolrCore.java:2006)
> at
> org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:777)
> at
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:413)
> at
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:204)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:455)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1075)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:384)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1009)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
> at
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
> at org.eclipse.jetty.server.Server.handle(Server.java:368)
> at
> org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)
> at
> org.eclipse.jetty.server.BlockingHttpConnection.handleRequest(BlockingHttpConnection.java:53)
> at
> org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:953)
> at
> org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1014)
> at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:861)
> at
> org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
> at
> org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:72)
> at
> org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:264)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalStateException: unexpected docvalues type
> NONE for field 'MediaType' (expected one of [SORTED, SORTED_SET]). Use
> UninvertingReader or index with docvalues.
> at org.apache.lucene.index.DocValues.checkField(DocValues.java:208)
> at
> org.apache.lucene.index.DocValues.getSortedSet(DocValues.java:306)
> at
> org.apache.lucene.search.grouping.term.TermGroupFacetCollector$MV.doSetNextReader(TermGroupFacetCollector.java:282)
> at
> org.apache.lucene.search.SimpleCollector.getLeafCollector(SimpleCollector.java:33)
> at
> org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:583)
> at
> org.apache.lucene.search.IndexSearcher.search(Ind

Parameterized values

[William Bell]

http://yonik.com/solr-query-parameter-substitution/

This is not working as part of QTs.

Cannot load the core, since ${value} is being used for XML parameters for
system property substitution.

https://wiki.apache.org/solr/SolrConfigXml#System_property_substitution

Can we support both?

PS127
hosp_quality_spec_boost:${pspec}


This does not work.


-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Parameterized values

[William Bell]

https://issues.apache.org/jira/browse/SOLR-7846

On Tue, Jul 28, 2015 at 11:16 AM, William Bell  wrote:

> http://yonik.com/solr-query-parameter-substitution/
>
> This is not working as part of QTs.
>
> Cannot load the core, since ${value} is being used for XML parameters for
> system property substitution.
>
> https://wiki.apache.org/solr/SolrConfigXml#System_property_substitution
>
> Can we support both?
>
> PS127
> hosp_quality_spec_boost:${pspec}
>
>
> This does not work.
>
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 720-256-8076
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Parameterized values

[William Bell]

That would be pretty bizarre.

I'll try it.

On Wed, Jul 29, 2015 at 1:00 PM, Mikhail Khludnev <
mkhlud...@griddynamics.com> wrote:

> hm. Did you try
> PS127
> hosp_quality_spec_boost:${pspec:${pspec}}
> ?
>
>
> On Tue, Jul 28, 2015 at 8:16 PM, William Bell  wrote:
>
> > http://yonik.com/solr-query-parameter-substitution/
> >
> > This is not working as part of QTs.
> >
> > Cannot load the core, since ${value} is being used for XML parameters for
> > system property substitution.
> >
> > https://wiki.apache.org/solr/SolrConfigXml#System_property_substitution
> >
> > Can we support both?
> >
> > PS127
> > hosp_quality_spec_boost:${pspec}
> >
> >
> > This does not work.
> >
> >
> > --
> > Bill Bell
> > billnb...@gmail.com
> > cell 720-256-8076
> >
>
>
>
> --
> Sincerely yours
> Mikhail Khludnev
> Principal Engineer,
> Grid Dynamics
>
> <http://www.griddynamics.com>
> 
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Why is /query needed for Json Facet?

[William Bell]

I tried using /select and this query does not work? Cannot understand why.
Passing Parameters via JSON

We can also pass normal request parameters in the JSON body within the
params block:
$ curl "http://localhost:8983/solr/query?fl=title,author"-d '
{
  params:{
q:"title:hero",
rows:1
  }
}
'

Which is equivalent to:
$ curl "http://localhost:8983/solr/query?fl=title
,author&q=title:hero&rows=1"


-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Why is /query needed for Json Facet?

[William Bell]

OK I figured it out. The documentation is not updated. The default
component are as follows:

FacetModule.COMPONENT_NAME = "facet_module"

Thus. The following is the default with the new facet_module.

We need someone to update the solrconfig.xml and the docs.



  query

  facet

 facet_module

  mlt

  highlight

  stats

  debug

  expand



 protected List getDefaultComponents()

  {

ArrayList names = new ArrayList<>(6);

names.add( QueryComponent.COMPONENT_NAME );

names.add( FacetComponent.COMPONENT_NAME );

names.add( FacetModule.COMPONENT_NAME );

names.add( MoreLikeThisComponent.COMPONENT_NAME );

names.add( HighlightComponent.COMPONENT_NAME );

names.add( StatsComponent.COMPONENT_NAME );

names.add( DebugComponent.COMPONENT_NAME );

names.add( ExpandComponent.COMPONENT_NAME);

return names;

  }



On Mon, Aug 3, 2015 at 11:31 AM, William Bell  wrote:

> I tried using /select and this query does not work? Cannot understand why.
> Passing Parameters via JSON
>
> We can also pass normal request parameters in the JSON body within the
> params block:
> $ curl "http://localhost:8983/solr/query?fl=title,author"-d '
> {
>   params:{
> q:"title:hero",
> rows:1
>   }
> }
> '
>
> Which is equivalent to:
> $ curl "http://localhost:8983/solr/query?fl=title
> ,author&q=title:hero&rows=1"
>
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 720-256-8076
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

SOLR 5.3

[William Bell]

When do we think SOLR 5.3 might come out?

It is nearly ready?

-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

jetty.xml

[William Bell]

We sometimes get a spike in Solr, and we get like 3K of threads and then
timeouts...

In Solr 5.2.1 the defult jetty settings is kinda crazy for threads - since
the value is HIGH!

What do others recommend?

Fusion jetty settings for Threads:




  

*  *

  

  false





This is better than SOLR default:


  









false

  

-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

SOLR 5.3

[William Bell]

At lucene.apache.org/solr it says SOLR 5.3 is there, but when I click on
downloads it shows Solr 5.2.1... ??

"APACHE SOLR™ 5.3.0Solr is the popular, blazing-fast, open source
enterprise search platform built on Apache Lucene™."

-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: DIH delta-import pk

[William Bell]

Send the SQL and Schema.xml. Also logs. Does it complain about _id_ or you
field in schema?




On Sun, Aug 23, 2015 at 4:55 AM, CrazyDiamond  wrote:

> Now  I set db id as unique field and uuid field,which should be generated
> automatically as required. but when i add document i have an error that my
> required uuid field is missing.
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/DIH-delta-import-pk-tp4224342p4224701.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Query timeAllowed and its behavior.

[William Bell]

As we reported, we are having issues with timeAllowed on 5.2.1. If we set a
timeAllowed=1 and then run the same query with timeAllowed=3 we get the
# of rows that was returned on the first query.

It appears the results are cached when exceeding the timeAllowed, like the
results are correct - when they are truncated.

SEEMS LIKE A BUG TO ME.

On Tue, Aug 25, 2015 at 5:16 AM, Jonathon Marks (BLOOMBERG/ LONDON) <
jmark...@bloomberg.net> wrote:

> timeAllowed applies to the time taken by the collector in each shard
> (TimeLimitingCollector). Once timeAllowed is exceeded the collector
> terminates early, returning any partial results it has and freeing the
> resources it was using.
> From Solr 5.0 timeAllowed also applies to the query expansion phase and
> SolrClient request retry.
>
> From: solr-user@lucene.apache.org At: Aug 25 2015 10:18:07
> Subject: Re:Query timeAllowed and its behavior.
>
> Hi,
>
> Kindly help me understand the query time allowed attribute. The following
> is set in solrconfig.xml.
> 30
>
> Does this setting stop the query from running after the timeAllowed is
> reached? If not is there a way to stop it as it will occupy resources in
> background for no benefit.
>
> Thanks,
> Modassar
>
>
>


-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: DataImportHandler scheduling

[William Bell]

We should add a simple scheduler in the UI. It is very useful. To schedule
various actions:

- Full index
- Delta Index
- Replicate




On Tue, Sep 1, 2015 at 12:41 PM, Shawn Heisey  wrote:

> On 9/1/2015 11:45 AM, Troy Edwards wrote:
> > My initial thought was to use scheduling built with DIH:
> > http://wiki.apache.org/solr/DataImportHandler#Scheduling
> >
> > But I think just a cron job should do the same for me.
>
> The dataimport scheduler does not exist in any Solr version.  This is a
> proposed feature, with the enhancement issue open for more than four years:
>
> https://issues.apache.org/jira/browse/SOLR-2305
>
> I have updated the wiki page to state the fact that the scheduler is a
> proposed improvement, not a usable feature.
>
> Thanks,
> Shawn
>
>


-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: solr training

[William Bell]

How about in Denver?

On Sun, Sep 13, 2015 at 7:53 PM, Otis Gospodnetić <
otis.gospodne...@gmail.com> wrote:

> Hi Tim,
>
> A slightly delayed reply ;)
> We are running Solr training in NYC next month -
> http://sematext.com/training/solr-training.html - 2nd seat is 50% off.
>
> Otis
> --
> Monitoring * Alerting * Anomaly Detection * Centralized Log Management
> Solr & Elasticsearch Support * http://sematext.com/
>
>
> On Fri, May 1, 2015 at 2:18 PM, Tim Dunphy  wrote:
>
> > Hey guys,
> >
> >  My company has a training budget that it wants me to use. So what I'd
> like
> > to find out is if there is any instructor lead courses in the NY/NJ area,
> > or courses online that are instructor lead that you could recommend?
> >
> > Thanks,
> > Tim
> >
> > --
> > GPG me!!
> >
> > gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
> >
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Ideas

[William Bell]

We have some Denial of service attacks on our web site. SOLR threads are
going crazy.

Basically someone is hitting start=15 + and rows=20. The start is crazy
large.

And then they jump around. start=15 then start=213030 etc.

Any ideas for how to stop this besides blocking these IPs?

Sometimes it is Google doing it even though these search results are set
with No-index and No-Follow on these pages.

Thoughts? Ideas?

Thanks

-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

FieldCache?

[William Bell]

So the FieldCache was removed from Solr 5.

What is the implication of this? Should we move all facets to DocValues
when we have high cardinality (lots of values) ? Are we adding it back?

Other ideas to improve performance?

>From Mike M:

FieldCache is gone (moved to a dedicated UninvertingReader in the miscmodule).
This means when you intend to sort on a field, you should index that field
using doc values, which is much faster and less heap consuming than
FieldCache.

-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

??

[William Bell]

http://www.slideshare.net/lucidworks/high-performance-solr-and-jvm-tuning-strategies-used-for-map-quests-search-ahead-darren-spehr

See ArrayBlockingQueue.

What would this help with?

-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

solr-user@lucene.apache.org

[William Bell]

What should this be set to?

Do you set it with -Dsolr.jetty.https.acceptQueueSize=5000 ?



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: AutoComplete Feature in Solr

[William Bell]

We want to use suggester but also want to show those results closest to my
lat,long... Kinda combine suggester and bq=geodist()

On Mon, Oct 12, 2015 at 2:24 PM, Salman Ansari 
wrote:

> Hi,
>
> I have been trying to get the autocomplete feature in Solr working with no
> luck up to now. First I read that "suggest component" is the recommended
> way as in the below article (and this is the exact functionality I am
> looking for, which is to autocomplete multiple words)
>
> http://blog.trifork.com/2012/02/15/different-ways-to-make-auto-suggestions-with-solr/
>
> Then I tried implementing suggest as described in the following articles in
> this order
> 1) https://wiki.apache.org/solr/Suggester#SearchHandler_configuration
> 2) http://solr.pl/en/2010/11/15/solr-and-autocomplete-part-2/  (I
> implemented suggesting phrases)
> 3)
>
> http://stackoverflow.com/questions/18132819/how-to-have-solr-autocomplete-on-whole-phrase-when-query-contains-multiple-terms
>
> With no luck, after implementing each article when I run my query as
> http://[MySolr]:8983/solr/entityStore114/suggest?spellcheck.q=Barack
>
>
>
> I get
> 
> 
> 0
> 0
> 
> 
>
>  Although I have an entry for Barack Obama in my index. I am posting my
> Solr configuration as well
>
> 
>  
>   suggest
>   org.apache.solr.spelling.suggest.Suggester
>name="lookupImpl">org.apache.solr.spelling.suggest.fst.FSTLookup
>   entity_autocomplete
> true
>  
> 
>
>   class="org.apache.solr.handler.component.SearchHandler">
>  
>   true
>   suggest
>   10
> true
> false
>  
>  
>   suggest
>  
> 
>
> It looks like a very simple job, but even after following so many articles,
> I could not get it right. Any comment will be appreciated!
>
> Regards,
> Salman
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Lucene Revolution ?

[William Bell]

How did Lucene Revolution 2015 go last week?

Also, what about Amazon's release of Elastic Search as a managed service in
AWS?

-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Add replication to http://localhost:8983/solr/#/~cores/extinfo

[William Bell]

It would be very useful to add a button to replicate (like we have
optimize) on

http://localhost:8983/solr/#/~cores/extinfo

Also a link to the core would be great too


-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

PayloadTermQuery deprecated

[William Bell]

Wondering how to change my payload based on example:

https://lucidworks.com/blog/2014/06/13/end-to-end-payload-example-in-solr/

PayloadTermQuery and BooleanQuery are deprecated in 5.3.x

@Override
public Query parse() throws SyntaxError {

if (qstr == null || qstr.length() == 0) return null;
BooleanQuery q = new BooleanQuery();
if (qstr.length() > 1 && qstr.startsWith("\"") && qstr.endsWith("\"")) {
qstr = qstr.substring(1,qstr.length()-1);
}
String[] nvps = StringUtils.split(qstr, " ");
for (int i = 0; i < nvps.length; i++) {
String[] nv = StringUtils.split(nvps[i], ":");
if (nv.length > 1) {
  if (nv[0].startsWith("+")) {
q.add(new PayloadTermQuery(new Term(nv[0].substring(1), nv[1]),
  new AveragePayloadFunction(), false), Occur.MUST);
  } else {
q.add(new PayloadTermQuery(new Term(nv[0], nv[1]),
  new AveragePayloadFunction(), false), Occur.SHOULD);
  }
}
}
return q;
}


-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Lucene Revolution ?

[William Bell]

Summary of new things in 5.x or 6.x that is catching fire? Ideas? Thoughts
on the Facet caching flame war?


On Sun, Oct 18, 2015 at 3:47 PM, Susheel Kumar 
wrote:

> I couldn't also make it.  Would love to hear more who make it.
>
> Thanks,
> Susheel
>
> On Sun, Oct 18, 2015 at 10:53 AM, Jack Krupansky  >
> wrote:
>
> > Sorry I missed out this year. I thought it was next month and hadn't seen
> > any reminders. Just last Tuesday I finally got around to googling the
> > conference and was shocked to read that it was the next day. Oh well.
> > Personally I'm less interested in the formal sessions than the informal
> > networking.
> >
> > In any case, keep those user reports flowing. I'm sure there are plenty
> of
> > people who didn't make it to the conference.
> >
> > -- Jack Krupansky
> >
> > On Sun, Oct 18, 2015 at 8:52 AM, Erik Hatcher 
> > wrote:
> >
> > > The Revolution was not televised (though heavily tweeted, and videos of
> > > sessions to follow eventually).  A great time was had by all.  Much
> > > learning!  Much collaboration. Awesome event if I may say so myself.
> I'm
> > > proud to be a part of the organization that put on the best conference
> > I've
> > > been to to date (til next years Revolution). Don't miss the next one :)
> > >
> > > Re ES/AWS: what about it?   Solr is a first class AWS citizen,
> employing
> > > Solr folks, and certainly where many of our customers deploy their
> > > infrastructure, Solr, Fusion, etc.
> > >
> > >Erik
> > >
> > >
> > >
> > > > On Oct 18, 2015, at 01:02, William Bell  wrote:
> > > >
> > > > How did Lucene Revolution 2015 go last week?
> > > >
> > > > Also, what about Amazon's release of Elastic Search as a managed
> > service
> > > in
> > > > AWS?
> > > >
> > > > --
> > > > Bill Bell
> > > > billnb...@gmail.com
> > > > cell 720-256-8076
> > >
> >
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: PayloadTermQuery deprecated

[William Bell]

Here is my first stab at it. Thoughts?

Question:

new PayloadTermQuery(new Term(nv[0].substring(1), nv[1]), new
AveragePayloadFunction(), false)

How do I handle the "false"  ? It means boolean includeSpanScore


@Override
public Query parse() throws SyntaxError {

if (qstr == null || qstr.length() == 0) return null;
//BooleanQuery q = new BooleanQuery();
BooleanQuery.Builder q = new BooleanQuery.Builder();
q.setDisableCoord(true);
if (qstr.length() > 1 && qstr.startsWith("\"") && qstr.endsWith("\"")) {
qstr = qstr.substring(1,qstr.length()-1);
}
String[] nvps = StringUtils.split(qstr, " ");
for (int i = 0; i < nvps.length; i++) {
String[] nv = StringUtils.split(nvps[i], ":");
if (nv.length > 1) {
  if (nv[0].startsWith("+")) {
  SpanTermQuery sq = new SpanTermQuery(new
Term(nv[0].substring(1), nv[1]));
  PayloadScoreQuery psq = new PayloadScoreQuery(sq, new
AveragePayloadFunction());
  q.add(psq, Occur.MUST);
//q.add(new PayloadTermQuery(new Term(nv[0].substring(1),
nv[1]), new AveragePayloadFunction(), false), Occur.MUST);
  } else {
//q.add(new PayloadTermQuery(new Term(nv[0], nv[1]), new
AveragePayloadFunction(), false), Occur.SHOULD);
  SpanTermQuery sq = new SpanTermQuery(new Term(nv[0], nv[1]));
  PayloadScoreQuery psq = new PayloadScoreQuery(sq, new
AveragePayloadFunction());
  q.add(psq, Occur.SHOULD);
  }
    }
}
// return q;
return q.build();
}


On Sun, Oct 18, 2015 at 4:46 PM, William Bell  wrote:

> Wondering how to change my payload based on example:
>
> https://lucidworks.com/blog/2014/06/13/end-to-end-payload-example-in-solr/
>
> PayloadTermQuery and BooleanQuery are deprecated in 5.3.x
>
> @Override
> public Query parse() throws SyntaxError {
>
> if (qstr == null || qstr.length() == 0) return null;
> BooleanQuery q = new BooleanQuery();
> if (qstr.length() > 1 && qstr.startsWith("\"") && qstr.endsWith("\"")) {
> qstr = qstr.substring(1,qstr.length()-1);
> }
> String[] nvps = StringUtils.split(qstr, " ");
> for (int i = 0; i < nvps.length; i++) {
> String[] nv = StringUtils.split(nvps[i], ":");
> if (nv.length > 1) {
>   if (nv[0].startsWith("+")) {
> q.add(new PayloadTermQuery(new Term(nv[0].substring(1), nv[1]),
>   new AveragePayloadFunction(), false), Occur.MUST);
>   } else {
> q.add(new PayloadTermQuery(new Term(nv[0], nv[1]),
>   new AveragePayloadFunction(), false), Occur.SHOULD);
>   }
> }
> }
> return q;
> }
>
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 720-256-8076
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: PayloadTermQuery deprecated

[William Bell]

Alan,

Does this code look equivalent? And how do I change PayLoadScoreQuery to do
a Custom Similarity?

PayloadScoreQuery psq = new PayloadScoreQuery(sq, new
AveragePayloadFunction());

@Override
public Query parse() throws SyntaxError {

if (qstr == null || qstr.length() == 0) return null;
//BooleanQuery q = new BooleanQuery();
BooleanQuery.Builder q = new BooleanQuery.Builder();
q.setDisableCoord(true);
if (qstr.length() > 1 && qstr.startsWith("\"") && qstr.endsWith("\"")) {
qstr = qstr.substring(1,qstr.length()-1);
}
String[] nvps = StringUtils.split(qstr, " ");
for (int i = 0; i < nvps.length; i++) {
String[] nv = StringUtils.split(nvps[i], ":");
if (nv.length > 1) {
  if (nv[0].startsWith("+")) {
  SpanTermQuery sq = new SpanTermQuery(new
Term(nv[0].substring(1), nv[1]));
  PayloadScoreQuery psq = new PayloadScoreQuery(sq, new
AveragePayloadFunction());
  q.add(psq, Occur.MUST);
//q.add(new PayloadTermQuery(new Term(nv[0].substring(1),
nv[1]), new AveragePayloadFunction(), false), Occur.MUST);
  } else {
//q.add(new PayloadTermQuery(new Term(nv[0], nv[1]), new
AveragePayloadFunction(), false), Occur.SHOULD);
  SpanTermQuery sq = new SpanTermQuery(new Term(nv[0], nv[1]));
  PayloadScoreQuery psq = new PayloadScoreQuery(sq, new
AveragePayloadFunction());
  q.add(psq, Occur.SHOULD);
  }
}
}
// return q;
return q.build();
}


On Mon, Oct 19, 2015 at 1:49 AM, Alan Woodward  wrote:

> Hi Bill,
>
> This looks like an oversight on my part when migrating the payload scoring
> queries - can you open a JIRA ticket to add 'includeSpanScore' as an option
> to PayloadScoreQuery?
>
> As a workaround, you should be able to use a custom similarity that
> returns 1 for all scores (see IndexSearcher.NON_SCORING_SIMILARITY for an
> implementation that returns 0, you could just clone that and change
> SimScorer.score())
>
> Alan Woodward
> www.flax.co.uk
>
>
> On 19 Oct 2015, at 00:39, William Bell wrote:
>
> > Here is my first stab at it. Thoughts?
> >
> > Question:
> >
> > new PayloadTermQuery(new Term(nv[0].substring(1), nv[1]), new
> > AveragePayloadFunction(), false)
> >
> > How do I handle the "false"  ? It means boolean includeSpanScore
> >
> >
> > @Override
> > public Query parse() throws SyntaxError {
> >
> >if (qstr == null || qstr.length() == 0) return null;
> >//BooleanQuery q = new BooleanQuery();
> >BooleanQuery.Builder q = new BooleanQuery.Builder();
> >q.setDisableCoord(true);
> >if (qstr.length() > 1 && qstr.startsWith("\"") &&
> qstr.endsWith("\"")) {
> >qstr = qstr.substring(1,qstr.length()-1);
> >}
> >String[] nvps = StringUtils.split(qstr, " ");
> >for (int i = 0; i < nvps.length; i++) {
> >String[] nv = StringUtils.split(nvps[i], ":");
> >if (nv.length > 1) {
> >  if (nv[0].startsWith("+")) {
> >  SpanTermQuery sq = new SpanTermQuery(new
> > Term(nv[0].substring(1), nv[1]));
> >  PayloadScoreQuery psq = new PayloadScoreQuery(sq, new
> > AveragePayloadFunction());
> >  q.add(psq, Occur.MUST);
> >//q.add(new PayloadTermQuery(new Term(nv[0].substring(1),
> > nv[1]), new AveragePayloadFunction(), false), Occur.MUST);
> >  } else {
> >//q.add(new PayloadTermQuery(new Term(nv[0], nv[1]), new
> > AveragePayloadFunction(), false), Occur.SHOULD);
> >  SpanTermQuery sq = new SpanTermQuery(new Term(nv[0],
> nv[1]));
> >  PayloadScoreQuery psq = new PayloadScoreQuery(sq, new
> > AveragePayloadFunction());
> >  q.add(psq, Occur.SHOULD);
> >  }
> >}
> >}
> >// return q;
> >return q.build();
> > }
> >
> >
> > On Sun, Oct 18, 2015 at 4:46 PM, William Bell 
> wrote:
> >
> >> Wondering how to change my payload based on example:
> >>
> >>
> https://lucidworks.com/blog/2014/06/13/end-to-end-payload-example-in-solr/
> >>
> >> PayloadTermQuery and BooleanQuery are deprecated in 5.3.x
> >>
> >> @Override
> >> public Query parse() throws SyntaxError {
> >>
> >>if (qstr == null || qstr.length() == 0) return null;
> >>BooleanQuery q = new BooleanQuery();
> >>if (qstr.length

Get this committed

[William Bell]

I can confirm this is working in PROD at 100M hits a day.

Can we commit it please? Begging here.

https://issues.apache.org/jira/browse/SOLR-7993

-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Get this committed

[William Bell]

OK I added the test case.

On Fri, Oct 23, 2015 at 5:05 AM, Shalin Shekhar Mangar <
shalinman...@gmail.com> wrote:

> I can review and commit if you add a test.
>
> On Fri, Oct 23, 2015 at 9:45 AM, William Bell  wrote:
> > I can confirm this is working in PROD at 100M hits a day.
> >
> > Can we commit it please? Begging here.
> >
> > https://issues.apache.org/jira/browse/SOLR-7993
> >
> > --
> > Bill Bell
> > billnb...@gmail.com
> > cell 720-256-8076
>
>
>
> --
> Regards,
> Shalin Shekhar Mangar.
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

any clean test failing

[William Bell]

It is getting stuck on resolve.

ant clean test

SOLR 5.3.1

[ivy:retrieve] retrieve done (5ms)

Overriding previous definition of property "ivy.version"

[ivy:retrieve] no resolved descriptor found: launching default resolve

Overriding previous definition of property "ivy.version"

[ivy:retrieve] using ivy parser to parse
file:/home/solr/src/lucene_solr_5_3_1A/solr/server/ivy.xml

[ivy:retrieve] :: resolving dependencies :: org.apache.solr#
example;work...@hgsolr2devmstr.healthgrades.com

[ivy:retrieve] confs: [logging]

[ivy:retrieve] validate = true

[ivy:retrieve] refresh = false

[ivy:retrieve] resolving dependencies for configuration 'logging'

[ivy:retrieve] == resolving dependencies for org.apache.solr#
example;work...@hgsolr2devmstr.healthgrades.com [logging]

[ivy:retrieve] == resolving dependencies
org.apache.solr#example;work...@hgsolr2devmstr.healthgrades.com->log4j#log4j;1.2.17
[logging->master]

[ivy:retrieve] default: Checking cache for: dependency: log4j#log4j;1.2.17
{logging=[master]}

[ivy:retrieve] don't use cache for log4j#log4j;1.2.17: checkModified=true

[ivy:retrieve] tried /home/solr/.ivy2/local/log4j/log4j/1.2.17/ivys/ivy.xml

[ivy:retrieve] tried
/home/solr/.ivy2/local/log4j/log4j/1.2.17/jars/log4j.jar

[ivy:retrieve] local: no ivy file nor artifact found for log4j#log4j;1.2.17

[ivy:retrieve] main: Checking cache for: dependency: log4j#log4j;1.2.17
{logging=[master]}

[ivy:retrieve] main: module revision found in cache: log4j#log4j;1.2.17

[ivy:retrieve] found log4j#log4j;1.2.17 in public

[ivy:retrieve] == resolving dependencies
org.apache.solr#example;work...@hgsolr2devmstr.healthgrades.com->org.slf4j#slf4j-api;1.7.7
[logging->master]

[ivy:retrieve] default: Checking cache for: dependency:
org.slf4j#slf4j-api;1.7.7 {logging=[master]}

[ivy:retrieve] don't use cache for org.slf4j#slf4j-api;1.7.7:
checkModified=true

[ivy:retrieve] tried
/home/solr/.ivy2/local/org.slf4j/slf4j-api/1.7.7/ivys/ivy.xml

[ivy:retrieve] tried
/home/solr/.ivy2/local/org.slf4j/slf4j-api/1.7.7/jars/slf4j-api.jar

[ivy:retrieve] local: no ivy file nor artifact found for
org.slf4j#slf4j-api;1.7.7

[ivy:retrieve] main: Checking cache for: dependency:
org.slf4j#slf4j-api;1.7.7 {logging=[master]}

[ivy:retrieve] main: module revision found in cache:
org.slf4j#slf4j-api;1.7.7

[ivy:retrieve] found org.slf4j#slf4j-api;1.7.7 in public

[ivy:retrieve] == resolving dependencies
org.apache.solr#example;work...@hgsolr2devmstr.healthgrades.com->org.slf4j#jcl-over-slf4j;1.7.7
[logging->master]

[ivy:retrieve] default: Checking cache for: dependency:
org.slf4j#jcl-over-slf4j;1.7.7 {logging=[master]}

[ivy:retrieve] don't use cache for org.slf4j#jcl-over-slf4j;1.7.7:
checkModified=true

-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: any clean test failing

[William Bell]

OK I deleted /home/solr/.ivy2 and it started working.

On Sat, Oct 24, 2015 at 11:57 AM, William Bell  wrote:

> It is getting stuck on resolve.
>
> ant clean test
>
> SOLR 5.3.1
>
> [ivy:retrieve] retrieve done (5ms)
>
> Overriding previous definition of property "ivy.version"
>
> [ivy:retrieve] no resolved descriptor found: launching default resolve
>
> Overriding previous definition of property "ivy.version"
>
> [ivy:retrieve] using ivy parser to parse
> file:/home/solr/src/lucene_solr_5_3_1A/solr/server/ivy.xml
>
> [ivy:retrieve] :: resolving dependencies :: org.apache.solr#
> example;work...@hgsolr2devmstr.healthgrades.com
>
> [ivy:retrieve] confs: [logging]
>
> [ivy:retrieve] validate = true
>
> [ivy:retrieve] refresh = false
>
> [ivy:retrieve] resolving dependencies for configuration 'logging'
>
> [ivy:retrieve] == resolving dependencies for org.apache.solr#
> example;work...@hgsolr2devmstr.healthgrades.com [logging]
>
> [ivy:retrieve] == resolving dependencies
> org.apache.solr#example;work...@hgsolr2devmstr.healthgrades.com->log4j#log4j;1.2.17
> [logging->master]
>
> [ivy:retrieve] default: Checking cache for: dependency: log4j#log4j;1.2.17
> {logging=[master]}
>
> [ivy:retrieve] don't use cache for log4j#log4j;1.2.17: checkModified=true
>
> [ivy:retrieve] tried
> /home/solr/.ivy2/local/log4j/log4j/1.2.17/ivys/ivy.xml
>
> [ivy:retrieve] tried
> /home/solr/.ivy2/local/log4j/log4j/1.2.17/jars/log4j.jar
>
> [ivy:retrieve] local: no ivy file nor artifact found for
> log4j#log4j;1.2.17
>
> [ivy:retrieve] main: Checking cache for: dependency: log4j#log4j;1.2.17
> {logging=[master]}
>
> [ivy:retrieve] main: module revision found in cache: log4j#log4j;1.2.17
>
> [ivy:retrieve] found log4j#log4j;1.2.17 in public
>
> [ivy:retrieve] == resolving dependencies
> org.apache.solr#example;work...@hgsolr2devmstr.healthgrades.com->org.slf4j#slf4j-api;1.7.7
> [logging->master]
>
> [ivy:retrieve] default: Checking cache for: dependency:
> org.slf4j#slf4j-api;1.7.7 {logging=[master]}
>
> [ivy:retrieve] don't use cache for org.slf4j#slf4j-api;1.7.7:
> checkModified=true
>
> [ivy:retrieve] tried
> /home/solr/.ivy2/local/org.slf4j/slf4j-api/1.7.7/ivys/ivy.xml
>
> [ivy:retrieve] tried
> /home/solr/.ivy2/local/org.slf4j/slf4j-api/1.7.7/jars/slf4j-api.jar
>
> [ivy:retrieve] local: no ivy file nor artifact found for
> org.slf4j#slf4j-api;1.7.7
>
> [ivy:retrieve] main: Checking cache for: dependency:
> org.slf4j#slf4j-api;1.7.7 {logging=[master]}
>
> [ivy:retrieve] main: module revision found in cache:
> org.slf4j#slf4j-api;1.7.7
>
> [ivy:retrieve] found org.slf4j#slf4j-api;1.7.7 in public
>
> [ivy:retrieve] == resolving dependencies
> org.apache.solr#example;work...@hgsolr2devmstr.healthgrades.com->org.slf4j#jcl-over-slf4j;1.7.7
> [logging->master]
>
> [ivy:retrieve] default: Checking cache for: dependency:
> org.slf4j#jcl-over-slf4j;1.7.7 {logging=[master]}
>
> [ivy:retrieve] don't use cache for org.slf4j#jcl-over-slf4j;1.7.7:
> checkModified=true
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 720-256-8076
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Looking for SOLR consulting help

[William Bell]

Healthgrades is looking for Solr consulting assistance.

Rate is negotiable based on skillsets. $125 - $175/hr

We are flexible on time.

1. Solr 5.x experience
2. Tuning performance
3. Relevancy and Autosuggest experience
4. Move to Solr Cloud
5. Amazon Linux Debian experience
6. Java experience using InteliJ and SOLRJ
7. Review requirements and implement changes to Solr cores/collections

Please email me directly, no agents.

Needed for 3-6 months. Could go full time.


-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Solr Suggester with Geo?

[William Bell]

http://lucidworks.com/blog/solr-suggester/


Wondering if anyone has uses these new techniques with a boost on
geodist() inverted? So the rows that get returned that are closest
need to come back first.


We are still using Edge Grams since we have not figured out how to
boost the results on geo spatial.


Anyone have thoughts?




-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Solr Suggester with Geo?

[William Bell]

Yeah we have that working today. But the issue is we want to use
http://lucidworks.com/blog/solr-suggester/

And you cannot do a boost with that right?



On Mon, Nov 9, 2015 at 12:41 PM, Sameer Maggon 
wrote:

> Have you looked at the Spatial extensions for Solr? If you are indexing
> Lat/Lon along with your documents, you can compute the distance from the
> origin & use that distance as one of the boost factors to affect the score.
> Typically, use cases around that combine the geo score with other factors
> as a pure sort by geo score might not give you the relevant results.
>
> e.g. typing to search for "sushi restaurants" near Santa Monica, CA - you
> might not want "thai restaurants" that are closest to you. (Local Search
> use case)
>
> https://cwiki.apache.org/confluence/display/solr/Spatial+Search
>
> Thanks,
> --
> *Sameer Maggon*
> www.measuredsearch.com <http://measuredsearch.com/>
> Fully Managed Solr-as-a-Service | Solr Consulting | Solr Support
>
>
>
> On Mon, Nov 9, 2015 at 11:18 AM, William Bell  wrote:
>
> > http://lucidworks.com/blog/solr-suggester/
> >
> >
> > Wondering if anyone has uses these new techniques with a boost on
> > geodist() inverted? So the rows that get returned that are closest
> > need to come back first.
> >
> >
> > We are still using Edge Grams since we have not figured out how to
> > boost the results on geo spatial.
> >
> >
> > Anyone have thoughts?
> >
> >
> >
> >
> > --
> > Bill Bell
> > billnb...@gmail.com
> > cell 720-256-8076
> >
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

fl=value equals?

[William Bell]

We are trying to look at a value, and change another value based on that.

For example, for national search we want to pass in radius=national, and
then set another variable equal to 0, else set the other variable = to
geodist() calculation.

We tried {!switch} but this only appears to work on fq/q. There is no
function for constants for equals

http://localhost:8983/solr/select?q=*:*&radius=national&b=if(equals($radius,'national'),0,geodist())

This does not work:

http://localhost:8983/solr/select?q=*:*&radius=national&b={!switch
case.national=0 default=geodist() v=$radius}

Ideas?



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: fl=value equals?

[William Bell]

I was able to get it to work kinda with a map().

http://localhost:8983/solr/select?q=*:*&radius=1&b=
<http://localhost:8983/solr/select?q=*:*&radius=national&b=if(equals($radius,%27national%27),0,geodist())>
map($radius,1,1,0,geodist())

Where 1= National

Do you have an example of a SearchComponent? It would be pretty easy to
copy map() and develop an equals() right?

if(equals($radius, 'national'), 0, geodist())

This would probably be useful for everyone.

On Tue, Nov 10, 2015 at 4:05 PM, Jan Høydahl  wrote:

> Where is your “b” parameter used? I think that instead of trying to set a
> new “b” http param (which solr will not evaluate as a function), you should
> instead try to insert your function or switch qParser directly where the
> “b” param is used, e.g. in a bq or similar.
>
> A bit heavy weight, but you could of course write a custom SearchComponent
> to construct your “b” parameter...
>
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
>
> > 10. nov. 2015 kl. 23.52 skrev William Bell :
> >
> > We are trying to look at a value, and change another value based on that.
> >
> > For example, for national search we want to pass in radius=national, and
> > then set another variable equal to 0, else set the other variable = to
> > geodist() calculation.
> >
> > We tried {!switch} but this only appears to work on fq/q. There is no
> > function for constants for equals
> >
> >
> http://localhost:8983/solr/select?q=*:*&radius=national&b=if(equals($radius,'national'),0,geodist())
> >
> > This does not work:
> >
> > http://localhost:8983/solr/select?q=*:*&radius=national&b={!switch
> > case.national=0 default=geodist() v=$radius}
> >
> > Ideas?
> >
> >
> >
> > --
> > Bill Bell
> > billnb...@gmail.com
> > cell 720-256-8076
>
>


-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: fl=value equals?

[William Bell]

How about we just add a new function called equals() and put into the
solution?

On Fri, Nov 13, 2015 at 11:36 AM, simon  wrote:

> Please do push your script to github - I (re)-compile custom code
> infrequently and never remember how to setup the environment.
>
> On Thu, Nov 12, 2015 at 5:14 AM, Upayavira  wrote:
>
> > Okay, makes sense. As to your question - making a new ValueSourceParser
> > that handles 'equals' sounds pretty straight-forward.
> >
> > If it helps, I have somewhere an Ant project that will unpack Solr and
> > compile custom components against it. I could push that to github or
> > something.
> >
> > Upayavira
> >
> > On Thu, Nov 12, 2015, at 07:59 AM, billnb...@gmail.com wrote:
> > > fl=$b tells me it works. Or I can do a sort=$b asc
> > >
> > > The idea is to calculate a score but only include geo if it is not a
> > > national search. Do we want to send in a parameter into the QT which
> > > allows us to omit geo from national searches
> > >
> > >
> > > Bill Bell
> > > Sent from mobile
> > >
> > > > On Nov 11, 2015, at 1:15 AM, Upayavira  wrote:
> > > >
> > > > I concur with Jan - what does b= do?
> > > >
> > > > Also asking, how did you identify that it worked?
> > > >
> > > > Upayavira
> > > >
> > > >> On Wed, Nov 11, 2015, at 02:58 AM, William Bell wrote:
> > > >> I was able to get it to work kinda with a map().
> > > >>
> > > >> http://localhost:8983/solr/select?q=*:*&radius=1&b=
> > > >> <
> >
> http://localhost:8983/solr/select?q=*:*&radius=national&b=if(equals($radius,%27national%27),0,geodist())
> > >
> > > >> map($radius,1,1,0,geodist())
> > > >>
> > > >> Where 1= National
> > > >>
> > > >> Do you have an example of a SearchComponent? It would be pretty easy
> > to
> > > >> copy map() and develop an equals() right?
> > > >>
> > > >> if(equals($radius, 'national'), 0, geodist())
> > > >>
> > > >> This would probably be useful for everyone.
> > > >>
> > > >> On Tue, Nov 10, 2015 at 4:05 PM, Jan Høydahl  >
> > > >> wrote:
> > > >>
> > > >>> Where is your “b” parameter used? I think that instead of trying to
> > set a
> > > >>> new “b” http param (which solr will not evaluate as a function),
> you
> > should
> > > >>> instead try to insert your function or switch qParser directly
> where
> > the
> > > >>> “b” param is used, e.g. in a bq or similar.
> > > >>>
> > > >>> A bit heavy weight, but you could of course write a custom
> > SearchComponent
> > > >>> to construct your “b” parameter...
> > > >>>
> > > >>> --
> > > >>> Jan Høydahl, search solution architect
> > > >>> Cominvent AS - www.cominvent.com
> > > >>>
> > > >>>> 10. nov. 2015 kl. 23.52 skrev William Bell :
> > > >>>>
> > > >>>> We are trying to look at a value, and change another value based
> on
> > that.
> > > >>>>
> > > >>>> For example, for national search we want to pass in
> > radius=national, and
> > > >>>> then set another variable equal to 0, else set the other variable
> =
> > to
> > > >>>> geodist() calculation.
> > > >>>>
> > > >>>> We tried {!switch} but this only appears to work on fq/q. There is
> > no
> > > >>>> function for constants for equals
> > > >>>
> >
> http://localhost:8983/solr/select?q=*:*&radius=national&b=if(equals($radius,'national'),0,geodist())
> > > >>>>
> > > >>>> This does not work:
> > > >>>>
> > > >>>>
> http://localhost:8983/solr/select?q=*:*&radius=national&b={!switch
> > > >>>> case.national=0 default=geodist() v=$radius}
> > > >>>>
> > > >>>> Ideas?
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>> --
> > > >>>> Bill Bell
> > > >>>> billnb...@gmail.com
> > > >>>> cell 720-256-8076
> > > >>
> > > >>
> > > >> --
> > > >> Bill Bell
> > > >> billnb...@gmail.com
> > > >> cell 720-256-8076
> >
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Parallel SQL / calcite adapter

[William Bell]

How is performance on Calcite?

On Fri, Nov 20, 2015 at 5:12 AM, Joel Bernstein  wrote:

> After reading https://calcite.apache.org/docs/tutorial.html, I think it
> should be possible to use the Solr's JDBC Driver with Calcites JDBC
> adapter.
>
> If you give it a try and run into any problems, please create a jira.
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Nov 19, 2015 at 7:58 PM, Joel Bernstein 
> wrote:
>
> > It's an interesting question. The JDBC driver is still very basic. It
> > would depend on how much of the JDBC spec needs to be implemented to
> > connect to Calcite/Drill.
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Thu, Nov 19, 2015 at 3:28 AM, Kai Gülzau 
> wrote:
> >
> >>
> >> We are currently evaluating calcite as a SQL facade for different Data
> >> Sources
> >>
> >> -  JDBC
> >>
> >> -  REST
> >>
> >> >SOLR
> >>
> >> -  ...
> >>
> >> I didn't found a "native" calcite adapter for solr (
> >> http://calcite.apache.org/docs/adapter.html).
> >>
> >> Is it a good idea to use the parallel sql feature (over jdbc) to connect
> >> calcite (or apache drill) to solr?
> >> Any suggestions?
> >>
> >>
> >> Thanks,
> >>
> >> Kai Gülzau
> >>
> >
> >
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

RptWithGeometrySpatialField

[William Bell]

David, et al.


2 questions.



Is this a good tradeoff for performance?

Also, RptWithGeometrySpatialField improved performance on what type of
searches? Does it support multivalued lat,lon fields?

Does LatLonType support multivalued lat,lon fields or only RPT allows for
this?


-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Migrating from cores to collections

[William Bell]

OK. Been using Cores for 4 years. Want to migrate to collections / Cloud.

Do we have to change our queries?

http://loadbalancer:8983/solr/corename/select?q=*:*

What does this become once we have the collection sharded? Do we need a
Load Balancer or just point to one box and run the new query? Or would it
be better to hit the LB in case one machine is no longer good to go?

http://loadbalancer:8983/solr/collectionname/select?q=*:*

What features would not yet be ready for sharded setups with SolrCloud? In
the past, facet counts were an issue, grouping? stats? as well as IDF for
sorting by scores. i.e. facet.field=specialties. We want the Cardiologist
specialty to have unique numbers across shards. So if shard1 has 4 people
with Cardiology, and shard2 has 2 people with Cardiology, we would want the
number to be 6. We would want facet.sort to work on counts... I guess we
could index another collection for facets and just use 1 machine for that?
But doesn't that defeat the purpose?

What is the best walk thru for SOLR 5.3.1 ?

Looking at https://wiki.apache.org/solr/SolrCloud

-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Migrating from cores to collections

[William Bell]

ok.

What about using DIH handler? Does it index in a SolrCloud setup ? Or how
would I convert a query to use SolrJ ?

On Mon, Nov 30, 2015 at 5:36 AM, Upayavira  wrote:

>
>
> On Sun, Nov 29, 2015, at 07:38 PM, William Bell wrote:
> > OK. Been using Cores for 4 years. Want to migrate to collections / Cloud.
> >
> > Do we have to change our queries?
> >
> > http://loadbalancer:8983/solr/corename/select?q=*:*
> >
> > What does this become once we have the collection sharded? Do we need a
> > Load Balancer or just point to one box and run the new query? Or would it
> > be better to hit the LB in case one machine is no longer good to go?
> >
> > http://loadbalancer:8983/solr/collectionname/select?q=*:*
> >
> > What features would not yet be ready for sharded setups with SolrCloud?
> > In
> > the past, facet counts were an issue, grouping? stats? as well as IDF for
> > sorting by scores. i.e. facet.field=specialties. We want the Cardiologist
> > specialty to have unique numbers across shards. So if shard1 has 4 people
> > with Cardiology, and shard2 has 2 people with Cardiology, we would want
> > the
> > number to be 6. We would want facet.sort to work on counts... I guess we
> > could index another collection for facets and just use 1 machine for
> > that?
> > But doesn't that defeat the purpose?
> >
> > What is the best walk thru for SOLR 5.3.1 ?
> >
> > Looking at https://wiki.apache.org/solr/SolrCloud
>
> 1. Your queries should stay (more or less) the same
> 2. If you name a collection the same as what you are using for a core,
> your base URL will remain the same
> 3. If you use SolrJ, then you would change to CloudSolrClient, which
> would feel quite different, but the SolrQuery objects should be
> interchangeable
> 4. If you use SolrJ, then you don't need a load balancer - SolrJ will do
> round robin against the Solr nodes for that collection. It will respond
> to failures far faster than an LB ever could (I've seen downed machines
> pulled in <200ms)
> 5. Regarding sharded setups, there's two scenarios to consider -
> distributed in general, and solrcloud in particular. Every search
> component must be enabled for distributed search (faceting,
> highlighting, grouping, etc, etc). Some of the newer ones may not have
> had distributed support implemented yet. Others, such as Joining, will
> require particular concern, and will work in only a subset of
> conditions.
> 6. For IDF, mostly, IDF balances itself across the shards. If it
> doesn't, then distributed IDF is available, but that has a cost in terms
> of additional network traffic.
> 7. Faceting should work just fine (as you describe) across shards. I
> would check specifically on newer faceting features though before
> assuming anything.
> 8. facet.sort+counts, have you tried it?
> 9. I would consider this to be a more up-to-date place to go:
> https://cwiki.apache.org/confluence/display/solr/SolrCloud
>
> Upayavira
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: New leader/replica solution for HDFS

[William Bell]

Use DocValues.

On Wed, Feb 25, 2015 at 3:14 PM, Joseph Obernberger  wrote:

> Thank you!  I'm mainly concerned about facet performance.  When we have
> indexing turned on, our facet performance suffers significantly.
> I will add replicas and measure the performance change.
>
> -Joe Obernberger
>
>
> On 2/25/2015 4:31 PM, Erick Erickson wrote:
>
>> bq: Is adding replicas going to increase search performance?
>>
>> Absolutely, assuming you've maxed out Solr. You can scale the SOLR
>> query/second rate nearly linearly by adding replicas regardless of
>> whether it's over HDFS or not.
>>
>> Having multiple replicas per shard _also_ increases fault tolerance,
>> so you get both. Even with HDFS, though, a single replica (just a
>> leader) per shard means that you don't have any redundancy if the
>> motherboard on that server dies even though HDFS has multiple copies
>> of the _data_.
>>
>> Best,
>> Erick
>>
>> On Wed, Feb 25, 2015 at 12:01 PM, Joseph Obernberger
>>  wrote:
>>
>>> I am also confused on this.  Is adding replicas going to increase search
>>> performance?  I'm not sure I see the point of any replicas when using
>>> HDFS.
>>> Is there one?
>>> Thank you!
>>>
>>> -Joe
>>>
>>>
>>> On 2/25/2015 10:57 AM, Erick Erickson wrote:
>>>
 bq: And the data sync between leader/replica is always a problem

 Not quite sure what you mean by this. There shouldn't need to be
 any synching in the sense that the index gets replicated, the
 incoming documents should be sent to each node (and indexed
 to HDFS) as they come in.

 bq: There is duplicate index computing on Replilca side.

 Yes, that's the design of SolrCloud, explicitly to provide data safety.
 If you instead rely on the leader to index and somehow pull that
 indexed form to the replica, then you will lose data if the leader
 goes down before sending the indexed form.

 bq: My thought is that the leader and the replica all bind to the same
 data
 index directory.

 This is unsafe. They would both then try to _write_ to the same
 index, which can easily corrupt indexes and/or all but the first
 one to access the index would be locked out.

 All that said, the HDFS triple-redundancy compounded with the
 Solr leaders/replicas redundancy means a bunch of extra
 storage. You can turn the HDFS replication down to 1, but that has
 other implications.

 Best,
 Erick

 On Tue, Feb 24, 2015 at 11:12 PM, longsan  wrote:

> We used HDFS as our Solr index storage and we really have a heavy
> update
> load. We had met much problems with current leader/replica solution.
> There
> is duplicate index computing on Replilca side. And the data sync
> between
> leader/replica is always a problem.
>
> As HDFS already provides data replication on data layer, could Solr
> provide
> just service layer replication?
>
> My thought is that the leader and the replica all bind to the same data
> index directory. And the leader will build up index for new request,
> the
> replica will just keep update the index version with the leader(such
> as a
> soft commit periodically? ). If the leader lost then the replica will
> take
> the duty immediately.
>
> Thanks for any suggestion of this idea.
>
>
>
>
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/New-leader-replica-
> solution-for-HDFS-tp4188735.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>

>>>
>


-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Slow cross-core joins

[William Bell]

I agree that join is slow. Adding fq on LocalParams is good. Has this been
added to {!lucene} and other calls like join ?



On Mon, Mar 2, 2015 at 2:00 PM, Gopal Patwa  wrote:

> You could give a try for this join contrib patch
>
> https://issues.apache.org/jira/browse/SOLR-4787
>
>
>
> On Mon, Mar 2, 2015 at 12:04 PM, Matt B  wrote:
>
> > I've recently inherited a Solr instance that is required to perform
> > numerous joins between two cores, usually as filter queries, similar to
> the
> > one below:
> >
> > q=firstName=Matt&fq=-({!to=emailAddress toIndex=accounts type=join
> > fromIndex=lists
> from=listValue}list_id:38f2-351b-11e4-9579-001e67654bce
> > OR {!to=emailDomain toIndex=accounts type=join fromIndex=lists
> > from=listValue}list_id:38f2-351b-11e4-9579-001e67654bce OR
> > {!to=emailDomainReversed toIndex=accounts type=join fromIndex=lists
> > from=listValue}list_id:38f2-351b-11e4-9579-001e67654bce)
> >
> > The accounts core is about 35GB with ~40,000,000 documents and the lists
> > core is about 9 GB with 90,,000 documents.  There may be anywhere
> from
> > one to one million documents in the lists core matching any particular
> > list_id.  The idea is to filter a search query on the accounts core to
> > include or exclude any documents with an email address, email domain, or
> > reverse email domain that is found within the lists core for a particular
> > list id.  The lists core is frequently updated on a daily basis with both
> > additions and deletions.
> >
> > Not surprisingly, such queries are very slow, usually taking minutes to
> > return any results.
> >
> > Are there any possible strategies to significantly increase the
> > performance of such queries?  The JVM max heap size is set to 16 GB and
> the
> > server has 64 GB RAM.
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: copy field from boolean to int

[William Bell]

Can you reindex? Just use 1,0.

On Tue, Mar 17, 2015 at 6:08 PM, Chris Hostetter 
wrote:

>
> Can you open a jira to add docValues support for BoolField? ... i can't
> think of any good reason not to directly support that in Solr for
> BoolField ... seems like just an oversight that slipped through the
> cracks.
>
>
> For now, your best bet is probably to use an UpdateProcessor ... maybe 2
> instances of RegexReplaceProcessorFactory to match "true" and "false" and
> replace them with "0" and "1" ?
>
>
> : Date: Tue, 17 Mar 2015 17:57:03 -0700
> : From: Kevin Osborn 
> : Reply-To: solr-user@lucene.apache.org
> : To: solr-user@lucene.apache.org
> : Subject: copy field from boolean to int
> :
> : I was hoping to use DocValues, but one of my fields is a boolean, which
> is
> : not currently supported by DocValues. I can use a copyField to convert my
> : boolean to a string. Is there is anyway to use a copyField to convert
> from
> : a boolean to a tint?
>
>
> -Hoss
> http://www.lucidworks.com/
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Using G1 with Apache Solr

[William Bell]

The issue we had with Java 8 was with DIH handler. We were using Rhino and
with the new implementation in Java 8, we had several Regex expression
issues...

We are almost ready to go now, since we moved away from Rhino and now use
Java.

Bill

On Wed, Mar 25, 2015 at 2:14 AM, Daniel Collins 
wrote:

> Interesting none the less Shawn :)
>
> We use G1GC on our servers, we were on Java 7 (64-bit, RHEL6), but are
> trying to migrate to Java 8 (which seems to cause more GC issues, so we
> clearly need to tweak our settings), will investigate 8u40 though.
>
> On 25 March 2015 at 04:23, Shawn Heisey  wrote:
>
> > On 3/24/2015 9:52 PM, Shawn Heisey wrote:
> > > On 3/24/2015 3:48 PM, Kamran Khawaja wrote:
> > >> I'm running Solr 4.7.2 with Java 7u75 with the following JVM params:
> >
> > I really got my wires crossed.  Kamran sent his message to the
> > hostpot-gc-use mailing list, not the solr-user list!
> >
> > Thanks,
> > Shawn
> >
> >
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: ZFS File System for SOLR 3.6 and SOLR 4

[William Bell]

How is performance on XFS when compared to ext4?

>From Otis:  noatime, nodiratime

http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201306.mbox/%3CCACtzgz1YwM5HDQO1R=2CdGxFmJnXcs4pyWRuaPJkKRc=eb8...@mail.gmail.com%3E

Large file systems seem to work well in both. I think the underlying
hardware does actually matter too. SSD vs HDD vs Y.

Several people love XFS at Amazon:
http://java.dzone.com/articles/tips-check-and-improve-your


On Sat, Mar 28, 2015 at 4:57 PM, Bill Bell  wrote:

> Is the an advantage for Xfs over ext4 for Solr ? Anyone done testing?
>
> Bill Bell
> Sent from mobile
>
>
> > On Mar 27, 2015, at 8:14 AM, Shawn Heisey  wrote:
> >
> >> On 3/27/2015 12:30 AM, abhi Abhishek wrote:
> >> i am trying to use ZFS as filesystem for my Linux Environment.
> are
> >> there any performance implications of using any filesystem other than
> >> ext-3/ext-4 with SOLR?
> >
> > That should work with no problem.
> >
> > The only time Solr tends to have problems is if you try to use a network
> > filesystem.  As long as it's a local filesystem and it implements
> > everything a program can typically expect from a local filesystem, Solr
> > should work perfectly.
> >
> > Because of the compatibility problems that the license for ZFS has with
> > the GPL, ZFS on Linux is probably not as well tested as other
> > filesystems like ext4, xfs, or btrfs, but I have not heard about any big
> > problems, so it's probably safe.
> >
> > Thanks,
> > Shawn
> >
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Solr went on recovery multiple time.

[William Bell]

How big is your index? -Xmx6g is pretty small in general.

On Mon, Mar 30, 2015 at 7:20 PM, sthita  wrote:

> Thanks Erick for the reply. These are the configurations.
>
> 1.Solr servers count : 4 (1 master , 3 slaves)
> 2.My initial and maximum memory allocations to each solr servers are :
> -Xms5g
> -Xmx6g
> 3. 5 running zookeepers
> 4. My index size in each solr server around: 48GB
> 5. Every sec merger add/delete 500 docs to/from solr
>
> yes, i checked the the ZK config timeout is 10sec. I will increase the
> timeout to 45sec, Hope that will help.
>
> ZK config :
>
> # The number of milliseconds of each tick
> tickTime=2000
> # The number of ticks that the initial
> # synchronization phase can take
> initLimit=10
> # The number of ticks that can pass between
> # sending a request and getting an acknowledgement
> syncLimit=5
>
>
>
>
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Solr-went-on-recovery-multiple-time-tp4196249p4196450.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Solr went on recovery multiple time.

[William Bell]

I would give it 32GB of RAM. And try to use SSD.

On Tue, Mar 31, 2015 at 12:50 AM, sthita  wrote:

> Hi Bill, My index size is around 48GB and contains around 8 million
> documents.
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Solr-went-on-recovery-multiple-time-tp4196249p4196504.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

DOcValues

[William Bell]

If I set indexed=true and docvalues=true, when I
facet=true&facet.field=manu_exact
will it use docValues or the Indexed version?

Also, does it help with "*Too many values for UnInvertedField faceting" ?*


*Do I need to set facet.method when using docvalues?*



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Facet

[William Bell]

We increased our number of terms (String) in a facet by 50,000.  Now we are
getting an error when we facet by this field - so we switched it to
facet.method=enum, and now the results come back. However, when we put it
into production we literally hit a wall (CPU went to 100% for 16 cores)
after about 30 minutes live.

We tried adding more machines to reduce the CPU, but it did not help. I am
wondering if CPU is a symptom... So we increased memory from 12GB to 16GB.
(the core size is 10GB). This is Solr 4.10.3.

What are some ideas? We are going to try docValues on the field. Does
anyone know if method=fc or method=enum works for docValue? I cannot find
any documentation on that.

We are thinking of splitting the field into 2 fields (fielda, fieldb). At
least the number will be less, but not sure if it will help memory?

The weird thing is for the first 30 minutes things are performing great.
Literally at like 10% CPU across 16 cores, not much memory and normal GC.

Originally the facet was a method=fc. Is there an issue with enum? We have
facet.threads=20 set, and not sure this is wise for a enum ?

What would you look at? Would you recommend turning off different caches
like fieldCache or filterCache?

-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: sort on facet.index?

[William Bell]

Yonik,

Are you supporting enum/fc/fcs? Or native lucene faceting?


On Thu, Apr 2, 2015 at 10:28 AM, Yonik Seeley  wrote:

> On Thu, Apr 2, 2015 at 10:25 AM, Ryan Josal  wrote:
> > Sorting the result set or the facets?  For the facets there is
> > facet.sort=index (lexicographically) and facet.sort=count.  So maybe you
> > are asking if you can sort by index, but reversed?  I don't think this is
> > possible, and it's a good question.
>
> The new facet module that will be in Solr 5.1 supports sorting both
> directions on both count and index order (as well as by statistics /
> bucket aggregations).
> http://yonik.com/json-facet-api/
>
> -Yonik
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: DOcValues

[William Bell]

Thank you. This is very understandable.

I heard the Strings limitation for DocValues goes away in 5.0?

On Fri, Apr 3, 2015 at 2:35 PM, Shalin Shekhar Mangar <
shalinman...@gmail.com> wrote:

> On Fri, Apr 3, 2015 at 12:52 PM, Toke Eskildsen 
> wrote:
>
> > Shalin Shekhar Mangar  wrote:
> > > The UnInvertedField method of faceting is no longer used in Solr.
> >
> > True. Un-inversion still takes place for non-DV-fields though (see
> > UnivertingReader, which seems to lead to
> > FieldCacheImpl.SortedDocValuesCache). But the wrapping is far nicer as
> > everything looks like DocValues now and it seems (guessing quite a bit
> > here) that the old 16M-limitation is gone.
> >
> >
> Yes, you are right. I didn't mean to imply that fields aren't un-inverted
> at all.
>
>
> > - Toke Eskildsen
> >
>
>
>
> --
> Regards,
> Shalin Shekhar Mangar.
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Upgraded to 4.10.3, highlighting performance unusably slow

[William Bell]

Has anyone looked at it?

On Sun, May 3, 2015 at 10:18 AM, jaime spicciati 
wrote:

> We ran into this as well on 4.10.3 (not related to an upgrade). It was
> identified during load testing when a small percentage of queries would
> take more than 20 seconds to return. We were able to isolate it by
> rerunning the same query multiple times and regardless of cache hits the
> queries would still take a long time to return. We used this method to
> narrow down the performance problem to a small number of very large records
> (many many fields in a single record).
>
> We fixed it by turning on hl.requireFieldMatch on the query so that only
> fields that have an actual hit are passed through the highlighter.
>
> Hopefully this helps,
> Jaime Spicciati
>
> On Sat, May 2, 2015 at 8:20 PM, Joel Bernstein  wrote:
>
> > Hi,
> >
> > Can you also include the details of your research that narrowed the issue
> > to the highlighter?
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Sat, May 2, 2015 at 5:27 PM, Ryan, Michael F. (LNG-DAY) <
> > michael.r...@lexisnexis.com> wrote:
> >
> > > Are you able to identify if there is a particular part of the code that
> > is
> > > slow?
> > >
> > > A simple way to do this is to use the jstack command (assuming your
> > server
> > > has the full JDK installed). You can run it like this:
> > > /path/to/java/bin/jstack PID
> > >
> > > If you run that a bunch of times while your highlight query is running,
> > > you might be able to spot the hotspot. Usually I'll do something like
> > this
> > > to see the stacktrace for the thread running the query:
> > > /path/to/java/bin/jstack PID | grep SearchHandler -B30
> > >
> > > A few more questions:
> > > - What are response times you are seeing before and after the upgrade?
> Is
> > > "unusably slow" 1 second, 10 seconds...?
> > > - If you run the exact same query multiple times, is it consistently
> > slow?
> > > Or is it only slow on the first run?
> > > - While the query is running, do you see high user CPU on your server,
> or
> > > high IO wait, or both? (You can check this with the top command or
> vmstat
> > > command in Linux.)
> > >
> > > -Michael
> > >
> > > -Original Message-
> > > From: Cheng, Sophia Kuen [mailto:sophia_ch...@hms.harvard.edu]
> > > Sent: Saturday, May 02, 2015 4:13 PM
> > > To: solr-user@lucene.apache.org
> > > Subject: Upgraded to 4.10.3, highlighting performance unusably slow
> > >
> > > Hello,
> > >
> > > We recently upgraded solr from 3.8.0 to 4.10.3.  We saw that this
> upgrade
> > > caused a incredible slowdown in our searches. We were able to narrow it
> > > down to the highlighting. The slowdown is extreme enough that we are
> > > holding back our release until we can resolve this.  Our research
> > indicated
> > > using TermVectors & FastHighlighter were the way to go, however this
> > still
> > > does nothing for the performance. I think we may be overlooking a
> crucial
> > > configuration, but cannot figure it out. I was hoping for some guidance
> > and
> > > help. Sorry for the long email, I wanted to provide enough information.
> > >
> > > Our documents are largely dynamic fields, and so we have been using ‘*’
> > as
> > > the field for highlighting. This is the same setting as in prior
> versions
> > > of solr use. The dynamic fields are of type ’text’ and we added
> > > customizations to the schema.xml for the type ’text’:
> > >
> > >  positionIncrementGap="100"
> > > storeOffsetsWithPositions="true" termVectors="true"
> termPositions="true"
> > > termOffsets="true">
> > >   
> > > 
> > > 
> > > 
> > > 
> > >  > > words="stopwords.txt" enablePositionIncrements="true"/>
> > >  generateWordParts="1"
> > > generateNumberParts="1" catenateWords="1" catenateNumbers="1"
> > > catenateAll="0" splitOnCaseChange="1"/>
> > > 
> > >  > > protected="protwords.txt"/>
> > >   
> > >   
> > > 
> > > 
> > > 
> > >  > > words="stopwords.txt" enablePositionIncrements="true"/>
> > >  generateWordParts="1"
> > > generateNumberParts="1" catenateWords="0" catenateNumbers="0"
> > > catenateAll="0" splitOnCaseChange="1"/>
> > > 
> > >  > > protected="protwords.txt"/>
> > >   
> > > 
> > >
> > > One of the two dynamic fields we use:
> > >
> > >  > > stored="true" required="false" multiValued="true"/>
> > >
> > > In our solrConfig.xml file, we have:
> > >
> > >   > > name="defaults"> explicit
> > >  13
> > >  true
> > >  true
> > >
> > > 
> > > tvComponent
> > > 
> > > 
> > > 
> > >   
> > >  > > class="solr.highlight.GapFragmenter">
> > >   
> > > 100
> > >   
> > > 
> > > 
> > >   
> > > 70
> > > 0.5
> > > [-\w
> > ,/\n\"']{20,200}
> > >   
> > > 
> > >
> > >  > > class="solr.highlight.HtmlFormatter">
> > >   
> > > 
> > > 
> > >   
> > > 
> > >
> > > 
> > >  > > class="solr.highlight.SimpleFragListBuilder"/>
> > >  

JSON

[William Bell]

Can we gt this one fixed? If the Body is empty don't through a Null Pointer
Exception?

Thanks

>* 
>http://localhost:8983/solr/gettingstarted/select?wt=json&indent=true&q=foundation";
;*
>* -H "Content-type:application/json"*

You're telling Solr the body encoding is JSON, but then you don't send any
body.
We could catch that error earlier perhaps, but it still looks like an error?

-Yonik

-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: JSON

[William Bell]

thanks

On Tue, May 19, 2015 at 11:38 PM, Shalin Shekhar Mangar <
shalinman...@gmail.com> wrote:

> Someone just opened https://issues.apache.org/jira/browse/SOLR-7574 which
> is exactly what you experienced.
>
> On Tue, May 19, 2015 at 8:34 PM, Shalin Shekhar Mangar <
> shalinman...@gmail.com> wrote:
>
> > That sounds reasonable. Please open a Jira issue.
> >
> > On Sat, May 16, 2015 at 9:22 AM, William Bell 
> wrote:
> >
> >> Can we gt this one fixed? If the Body is empty don't through a Null
> >> Pointer
> >> Exception?
> >>
> >> Thanks
> >>
> >> >*
> >>
> http://localhost:8983/solr/gettingstarted/select?wt=json&indent=true&q=foundation
> >> "
> >> <
> >>
> http://localhost:8983/solr/gettingstarted/select?wt=json&indent=true&q=foundation%22
> >> >;*
> >> >* -H "Content-type:application/json"*
> >>
> >> You're telling Solr the body encoding is JSON, but then you don't send
> any
> >> body.
> >> We could catch that error earlier perhaps, but it still looks like an
> >> error?
> >>
> >> -Yonik
> >>
> >> --
> >> Bill Bell
> >> billnb...@gmail.com
> >> cell 720-256-8076
> >>
> >
> >
> >
> > --
> > Regards,
> > Shalin Shekhar Mangar.
> >
>
>
>
> --
> Regards,
> Shalin Shekhar Mangar.
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Applying gzip compression in Solr 5.1

[William Bell]

OK I got mine to work with 4.10.4 and it also works on 5.1...

mkdir war cp ../solr-4.10.4/example/webapps/solr.war . jar xvf
solr.war cd WEB-INF vi web.xmlAdd this above the  already
there:GzipFilter
org.eclipse.jetty.servlets.GzipFilter
   mimeTypes
   
application/xml,application/json,text/html,text/plain,text/xml,application/xhtml+xml,text/css,application/javascript,image/svg+xml,application/x-javascript,text/css

GzipFilter
/* cd .. rm solr.war
jar cvf solr.war * cp solr.war ../solr-4.10.4/example/webapps/solr.war
get jetty-servlets-8.1.10.v20130312.jar from
http://www.eclipse.org/downloads/download.php?file=/jetty/updates/jetty-bundles-8.x/8.1.10.v20130312/Jetty-bundles-repository-8.1.10.v20130312.zip&mirror_id=454
(notice the name has to be exactly that) and put into
solr-4.10.4/example/lib restart


On Thu, May 21, 2015 at 11:31 PM, Zheng Lin Edwin Yeo 
wrote:

> Hi,
>
> I'm trying to apply gzip compression in Solr 5.1. I understand that Running
> Solr on Tomcat is no longer supported from Solr 5.0, so I've tried to
> implement it in Solr.
>
> I've downloaded jetty-servlets-9.3.0.RC0.jar and placed it in my
> webapp\WEB-INF folder, and have added the following in
> webapp\WEB-INF\web.xml
>
>   
> GzipFilter
> org.eclipse.jetty.servlets.GzipFilter
> 
>   methods
>   GET,POST
>   mimeTypes
>
>
> text/html;charset=UTF-8,text/plain,text/xml,text/json,text/javascript,text/css,text/plain;charset=UTF-8,application/xhtml+xml,application/javascript,image/svg+xml,application/json,application/xml;
> charset=UTF-8
> 
>   
>   
> GzipFilter
> /*
>   
>
>
> However, when I start Solr and check the browser, there's no gzip
> compression. Is there anything which I configure wrongly or might have
> missed out? I'm also running zookeeper-3.4.6.
>
>
> Regards,
> Edwin
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Applying gzip compression in Solr 5.1

[William Bell]

You need to edit the web.xml as I stated above and put the solr.war file
back.

Instead of "example" it is "server". Note: 4.10.4 and 5.1.0 uses the same
Jetty. 8.1.10.v20130312

Here is the procedure for 5.1:

mkdir war
 cp ../solr-5.1.0/example/webapps/solr.war .
 jar xvf solr.war
 cd WEB-INF
 vi web.xml

Add this above the  already there (and save it after adding this).

GzipFilter
org.eclipse.jetty.servlets.GzipFilter
mimeTypes
 
application/xml,application/json,text/html,text/plain,text/xml,application/xhtml+xml,text/css,application/javascript,image/svg+xml,application/x-javascript,text/css
   



GzipFilter
/*

 cd ..
 rm solr.war
 jar cvf solr.war *
 cp solr.war ../solr-5.1.0/example/webapps/solr.war
 get jetty-servlets-8.1.10.v20130312.jar from
http://www.eclipse.org/downloads/download.php?file=/jetty/updates/jetty-bundles-8.x/8.1.10.v20130312/Jetty-bundles-repository-8.1.10.v20130312.zip&mirror_id=454
 (notice the name has to be exactly that) and put into solr-5.1.0/example/lib

 restart


On Sun, May 24, 2015 at 8:26 PM, Zheng Lin Edwin Yeo 
wrote:

> Thanks for your reply.
> Do we still have to use back the solr.war file in Solr 5.1 in order to get
> the gzip working?
>
>
> Regards,
> Edwin
>
>
>
> On 25 May 2015 at 06:57, William Bell  wrote:
>
> > OK I got mine to work with 4.10.4 and it also works on 5.1...
> >
> > mkdir war cp ../solr-4.10.4/example/webapps/solr.war . jar xvf
> > solr.war cd WEB-INF vi web.xmlAdd this above the  already
> > there:GzipFilter
> > org.eclipse.jetty.servlets.GzipFilter
> >mimeTypes
> >
> >
> application/xml,application/json,text/html,text/plain,text/xml,application/xhtml+xml,text/css,application/javascript,image/svg+xml,application/x-javascript,text/css
> > 
> > GzipFilter
> > /* cd .. rm solr.war
> > jar cvf solr.war * cp solr.war ../solr-4.10.4/example/webapps/solr.war
> > get jetty-servlets-8.1.10.v20130312.jar from
> >
> >
> http://www.eclipse.org/downloads/download.php?file=/jetty/updates/jetty-bundles-8.x/8.1.10.v20130312/Jetty-bundles-repository-8.1.10.v20130312.zip&mirror_id=454
> > (notice the name has to be exactly that) and put into
> > solr-4.10.4/example/lib restart
> >
> >
> > On Thu, May 21, 2015 at 11:31 PM, Zheng Lin Edwin Yeo <
> > edwinye...@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > I'm trying to apply gzip compression in Solr 5.1. I understand that
> > Running
> > > Solr on Tomcat is no longer supported from Solr 5.0, so I've tried to
> > > implement it in Solr.
> > >
> > > I've downloaded jetty-servlets-9.3.0.RC0.jar and placed it in my
> > > webapp\WEB-INF folder, and have added the following in
> > > webapp\WEB-INF\web.xml
> > >
> > >   
> > > GzipFilter
> > > org.eclipse.jetty.servlets.GzipFilter
> > > 
> > >   methods
> > >   GET,POST
> > >   mimeTypes
> > >
> > >
> > >
> >
> text/html;charset=UTF-8,text/plain,text/xml,text/json,text/javascript,text/css,text/plain;charset=UTF-8,application/xhtml+xml,application/javascript,image/svg+xml,application/json,application/xml;
> > > charset=UTF-8
> > > 
> > >   
> > >   
> > > GzipFilter
> > > /*
> > >   
> > >
> > >
> > > However, when I start Solr and check the browser, there's no gzip
> > > compression. Is there anything which I configure wrongly or might have
> > > missed out? I'm also running zookeeper-3.4.6.
> > >
> > >
> > > Regards,
> > > Edwin
> > >
> >
> >
> >
> > --
> > Bill Bell
> > billnb...@gmail.com
> > cell 720-256-8076
> >
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Applying gzip compression in Solr 5.1

[William Bell]

Err.. Here is the procedure for 5.1:

 mkdir war
 cp ../solr-5.1.0/server/webapps/solr.war .
 jar xvf solr.war
 cd WEB-INF
 vi web.xml

Add this above the  already there (and save it after adding this).

GzipFilter
org.eclipse.jetty.servlets.GzipFilter

mimeTypes
 
application/xml,application/json,text/html,text/plain,text/xml,application/xhtml+xml,text/css,application/javascript,image/svg+xml,application/x-javascript,text/css




GzipFilter
/*

 cd ..
 rm solr.war
 jar cvf solr.war *
 cp solr.war ../solr-5.1.0/server/webapps/solr.war
 get jetty-servlets-8.1.10.v20130312.jar from
http://www.eclipse.org/downloads/download.php?file=/jetty/updates/jetty-bundles-8.x/8.1.10.v20130312/Jetty-bundles-repository-8.1.10.v20130312.zip&mirror_id=454
 (notice the name has to be exactly that) and put into solr-5.1.0/server/lib

 restart


On Mon, May 25, 2015 at 8:42 PM, William Bell  wrote:

> You need to edit the web.xml as I stated above and put the solr.war file
> back.
>
> Instead of "example" it is "server". Note: 4.10.4 and 5.1.0 uses the same
> Jetty. 8.1.10.v20130312
>
> Here is the procedure for 5.1:
>
> mkdir war
>  cp ../solr-5.1.0/example/webapps/solr.war .
>  jar xvf solr.war
>  cd WEB-INF
>  vi web.xml
>
> Add this above the  already there (and save it after adding this).
> 
> GzipFilter
> org.eclipse.jetty.servlets.GzipFilter
> mimeTypes
>  
> application/xml,application/json,text/html,text/plain,text/xml,application/xhtml+xml,text/css,application/javascript,image/svg+xml,application/x-javascript,text/css
> 
> 
>
> 
> GzipFilter
> /*
> 
>  cd ..
>  rm solr.war
>  jar cvf solr.war *
>  cp solr.war ../solr-5.1.0/example/webapps/solr.war
>  get jetty-servlets-8.1.10.v20130312.jar from 
> http://www.eclipse.org/downloads/download.php?file=/jetty/updates/jetty-bundles-8.x/8.1.10.v20130312/Jetty-bundles-repository-8.1.10.v20130312.zip&mirror_id=454
>  (notice the name has to be exactly that) and put into solr-5.1.0/example/lib
>
>  restart
>
>
> On Sun, May 24, 2015 at 8:26 PM, Zheng Lin Edwin Yeo  > wrote:
>
>> Thanks for your reply.
>> Do we still have to use back the solr.war file in Solr 5.1 in order to get
>> the gzip working?
>>
>>
>> Regards,
>> Edwin
>>
>>
>>
>> On 25 May 2015 at 06:57, William Bell  wrote:
>>
>> > OK I got mine to work with 4.10.4 and it also works on 5.1...
>> >
>> > mkdir war cp ../solr-4.10.4/example/webapps/solr.war . jar xvf
>> > solr.war cd WEB-INF vi web.xmlAdd this above the  already
>> > there:GzipFilter
>> > org.eclipse.jetty.servlets.GzipFilter
>> >mimeTypes
>> >
>> >
>> application/xml,application/json,text/html,text/plain,text/xml,application/xhtml+xml,text/css,application/javascript,image/svg+xml,application/x-javascript,text/css
>> > 
>> > GzipFilter
>> > /* cd .. rm solr.war
>> > jar cvf solr.war * cp solr.war ../solr-4.10.4/example/webapps/solr.war
>> > get jetty-servlets-8.1.10.v20130312.jar from
>> >
>> >
>> http://www.eclipse.org/downloads/download.php?file=/jetty/updates/jetty-bundles-8.x/8.1.10.v20130312/Jetty-bundles-repository-8.1.10.v20130312.zip&mirror_id=454
>> > (notice the name has to be exactly that) and put into
>> > solr-4.10.4/example/lib restart
>> >
>> >
>> > On Thu, May 21, 2015 at 11:31 PM, Zheng Lin Edwin Yeo <
>> > edwinye...@gmail.com>
>> > wrote:
>> >
>> > > Hi,
>> > >
>> > > I'm trying to apply gzip compression in Solr 5.1. I understand that
>> > Running
>> > > Solr on Tomcat is no longer supported from Solr 5.0, so I've tried to
>> > > implement it in Solr.
>> > >
>> > > I've downloaded jetty-servlets-9.3.0.RC0.jar and placed it in my
>> > > webapp\WEB-INF folder, and have added the following in
>> > > webapp\WEB-INF\web.xml
>> > >
>> > >   
>> > > GzipFilter
>> > > org.eclipse.jetty.servlets.GzipFilter
>> > > 
>> > >   methods
>> > >   GET,POST
>> > >   mimeTypes
>> > >
>> > >
>> > >
>> >
>> text/html;charset=UTF-8,text/plain,text/xml,text/json,text/javascript,text/css,text/plain;charset=UTF-8,application/xhtml+xml,application/javascript,image/svg+xml,application/json,application/xml;
>> > > charset=UTF-8
>> > > 
>> > >   
>> > >   
>> > > GzipFilter
>> > > /*
>> > >   
>> > >
>> > >
>> > > However, when I start Solr and check the browser, there's no gzip
>> > > compression. Is there anything which I configure wrongly or might have
>> > > missed out? I'm also running zookeeper-3.4.6.
>> > >
>> > >
>> > > Regards,
>> > > Edwin
>> > >
>> >
>> >
>> >
>> > --
>> > Bill Bell
>> > billnb...@gmail.com
>> > cell 720-256-8076
>> >
>>
>
>
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 720-256-8076
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Running Solr 5.1.0 as a Service on Windows

[William Bell]

Why don't we change the bin/run -d to have Common Daemons? This would be a
great enhancement to SOLR 5.x.

We would switch to this if it was integrated. We currently use RunIt. But
love Common Daemons.

http://smarden.org/runit/
http://commons.apache.org/proper/commons-daemon/


On Thu, Jun 4, 2015 at 3:52 AM, Guillaume Belrose <
guillaume.belr...@quantel.com> wrote:

>
> Hi,
>
> I've successfully used procrun (see
> http://commons.apache.org/proper/commons-daemon/procrun.html) to wrap
> Solr 5.1 solr.cmd script as a Windows service (I’ve only tested on Windows
> 2008 R2). Previously, I was using Procrun to manage Jetty services running
> the Solr.war from older versions but with a bit a tweaking, I was able to
> wrap the new Solr 5.1.0 scripts.
>
> I roughly did the following:
> -download and unzip the Solr 5.1.0 distribution to a local folder (i.e.
> c:\opt )
> -download and unzip the Apache Commons Daemon .zip file (from
> http://commons.apache.org/proper/commons-daemon/download_daemon.cgi) in
> my solr local folder (i.e. c:\opt\solr-5.1.0)
> -run the batch file [1].
>
> All of this was done through Ansible Playbooks which is the tool I use for
> configuration management on Windows and Linux.
>
> Cheers,
>
> Guillaume.
>
> [1]
> @echo off
> set SERVICE_NAME=solr
> set SERVICE_HOME=c:\opt\solr-5.1.0
> set PR_INSTALL=%SERVICE_HOME%\amd64\prunsrv.exe
>
> @REM Service Log Configuration
> set PR_LOGPREFIX=%SERVICE_NAME%
> set PR_LOGPATH=%SERVICE_HOME%\logs
> set PR_STDOUTPUT=auto
> set PR_STDERROR=auto
> set PR_LOGLEVEL=Debug
>
> set PR_STARTUP=auto
> set PR_STARTMODE=exe
> set PR_STARTIMAGE=%SERVICE_HOME%\bin\solr.cmd
> set PR_STARTPARAMS=start
>
> @REM Shutdown Configuration
> set PR_STOPMODE=exe
> set PR_STOPIMAGE=%SERVICE_HOME%\bin\solr.cmd
> set PR_STOPPARAMS=stop -p 8983
>
> %PR_INSTALL% //IS/%SERVICE_NAME% ^
>   --Description="Solr-5.1.0" ^
>   --DisplayName="%SERVICE_NAME%" ^
>   --Install="%PR_INSTALL%" ^
>   --Startup="%PR_STARTUP%" ^
>   --LogPath="%PR_LOGPATH%" ^
>   --LogPrefix="%PR_LOGPREFIX%" ^
>   --LogLevel="%PR_LOGLEVEL%" ^
>   --StdOutput="%PR_STDOUTPUT%" ^
>   --StdError="%PR_STDERROR%" ^
>   --StartMode="%PR_STARTMODE%" ^
>   --StartImage="%PR_STARTIMAGE%" ^
>   --StartParams="%PR_STARTPARAMS%" ^
>   --StopMode="%PR_STOPMODE%" ^
>   --StopImage="%PR_STOPIMAGE%" ^
>   --StopParams="%PR_STOPPARAMS%"
>
> if not errorlevel 1 goto installed
> echo Failed to install "%SERVICE_NAME%" service.  Refer to log in
> %PR_LOGPATH%
> exit /B 1
>
> :installed
> echo The Service "%SERVICE_NAME%" has been installed
> exit /B 0
>
> ---
> This email has been scanned for email related threats and delivered safely
> by Mimecast.
> For more information please visit http://www.mimecast.com
>
> ---
>
>


-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Re: Running Solr 5.1.0 as a Service on Windows

[William Bell]

https://issues.apache.org/jira/browse/SOLR-7644

On Sun, Jun 7, 2015 at 11:54 AM, William Bell  wrote:

> Why don't we change the bin/run -d to have Common Daemons? This would be a
> great enhancement to SOLR 5.x.
>
> We would switch to this if it was integrated. We currently use RunIt. But
> love Common Daemons.
>
> http://smarden.org/runit/
> http://commons.apache.org/proper/commons-daemon/
>
>
> On Thu, Jun 4, 2015 at 3:52 AM, Guillaume Belrose <
> guillaume.belr...@quantel.com> wrote:
>
>>
>> Hi,
>>
>> I've successfully used procrun (see
>> http://commons.apache.org/proper/commons-daemon/procrun.html) to wrap
>> Solr 5.1 solr.cmd script as a Windows service (I’ve only tested on Windows
>> 2008 R2). Previously, I was using Procrun to manage Jetty services running
>> the Solr.war from older versions but with a bit a tweaking, I was able to
>> wrap the new Solr 5.1.0 scripts.
>>
>> I roughly did the following:
>> -download and unzip the Solr 5.1.0 distribution to a local folder (i.e.
>> c:\opt )
>> -download and unzip the Apache Commons Daemon .zip file (from
>> http://commons.apache.org/proper/commons-daemon/download_daemon.cgi) in
>> my solr local folder (i.e. c:\opt\solr-5.1.0)
>> -run the batch file [1].
>>
>> All of this was done through Ansible Playbooks which is the tool I use
>> for configuration management on Windows and Linux.
>>
>> Cheers,
>>
>> Guillaume.
>>
>> [1]
>> @echo off
>> set SERVICE_NAME=solr
>> set SERVICE_HOME=c:\opt\solr-5.1.0
>> set PR_INSTALL=%SERVICE_HOME%\amd64\prunsrv.exe
>>
>> @REM Service Log Configuration
>> set PR_LOGPREFIX=%SERVICE_NAME%
>> set PR_LOGPATH=%SERVICE_HOME%\logs
>> set PR_STDOUTPUT=auto
>> set PR_STDERROR=auto
>> set PR_LOGLEVEL=Debug
>>
>> set PR_STARTUP=auto
>> set PR_STARTMODE=exe
>> set PR_STARTIMAGE=%SERVICE_HOME%\bin\solr.cmd
>> set PR_STARTPARAMS=start
>>
>> @REM Shutdown Configuration
>> set PR_STOPMODE=exe
>> set PR_STOPIMAGE=%SERVICE_HOME%\bin\solr.cmd
>> set PR_STOPPARAMS=stop -p 8983
>>
>> %PR_INSTALL% //IS/%SERVICE_NAME% ^
>>   --Description="Solr-5.1.0" ^
>>   --DisplayName="%SERVICE_NAME%" ^
>>   --Install="%PR_INSTALL%" ^
>>   --Startup="%PR_STARTUP%" ^
>>   --LogPath="%PR_LOGPATH%" ^
>>   --LogPrefix="%PR_LOGPREFIX%" ^
>>   --LogLevel="%PR_LOGLEVEL%" ^
>>   --StdOutput="%PR_STDOUTPUT%" ^
>>   --StdError="%PR_STDERROR%" ^
>>   --StartMode="%PR_STARTMODE%" ^
>>   --StartImage="%PR_STARTIMAGE%" ^
>>   --StartParams="%PR_STARTPARAMS%" ^
>>   --StopMode="%PR_STOPMODE%" ^
>>   --StopImage="%PR_STOPIMAGE%" ^
>>   --StopParams="%PR_STOPPARAMS%"
>>
>> if not errorlevel 1 goto installed
>> echo Failed to install "%SERVICE_NAME%" service.  Refer to log in
>> %PR_LOGPATH%
>> exit /B 1
>>
>> :installed
>> echo The Service "%SERVICE_NAME%" has been installed
>> exit /B 0
>>
>> ---
>> This email has been scanned for email related threats and delivered
>> safely by Mimecast.
>> For more information please visit http://www.mimecast.com
>>
>> ---
>>
>>
>
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 720-256-8076
>



-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

SolrCloud across Amazon Regions?

[William Bell]

Here is a weird architecture...

We have a SOLR Master today, next to our database in our local data center.
We do Solr replication to Amazon East and West coasts once the index is
completed.

We would like to deploy Solr Cloud while leaving the master in place.

1. Local has SQL Server, and Solr Master.
2. We would like to replicate to EAST 2 machines, and WEST 2 machines.
3. The 2 machines on the East coast - we want to increase to 3, and use Zoo
Keeper to keep the configs in sync with the Master local. And we would like
to use Sharding/Collections to split the core into a collection across 3
machines for performance.

Indexing can stay local.

I understand that this is not normal, and maybe we can still use Master
replication with Sharinding/or Solr Cloud ? ideas?

-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Dataimport failing on SOLR 5.2

[William Bell]

   1. When I click "DataImport" in the UI on any core.. The UI just spins:
   2.
   3.
   
http://hgsolr2devmstr:8983/solr/autosuggest/admin/mbeans?cat=QUERYHANDLER&wt=json&_=1433749812067

Here is the response: 200:

{"responseHeader":{"status":0,"QTime":1},"solr-mbeans":["QUERYHANDLER",{"allcondalpha":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"autospecportal":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"autosuggestallpracproc":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"joinhomecondnopt":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"allprocalpha":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"autopayorportal":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"joinhomespec":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"/update/json":{"class":"org.apache.solr.handler.UpdateRequestHandler","version":"5.2.0","description":"Add
documents using XML (with XSLT), CSV, JSON, or
javabin","src":null},"joinhomepracspecnopt":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"autoall2":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"joinhomespeclocation":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"autosuggestallpraccond":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"/admin":{"class":"org.apache.solr.handler.admin.AdminHandlers","version":"5.2.0","description":"Register
Standard Admin
Handlers","src":null},"autocondportal":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"autoeduportal":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"/debug/dump":{"class":"org.apache.solr.handler.DumpRequestHandler","version":"5.2.0","description":"Dump
handler
(debug)","src":null},"/admin/mbeans":{"class":"org.apache.solr.handler.admin.SolrInfoMBeanHandler","version":"5.2.0","description":"Get
Info (and statistics) for registered
SolrInfoMBeans","src":null},"exactmatch2":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"/update/json/docs":{"class":"org.apache.solr.handler.UpdateRequestHandler","version":"5.2.0","description":"Add
documents using XML (with XSLT), CSV, JSON, or
javabin","src":null},"autopracall":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"joinautopraccond2":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"joinautopracproc2":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"/admin/properties":{"class":"org.apache.solr.handler.admin.PropertiesRequestHandler","version":"5.2.0","description":"Get
System
Properties","src":null},"autocohort":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"/admin/threads":{"class":"org.apache.solr.handler.admin.ThreadDumpHandler","version":"5.2.0","description":"Thread
Dump","src":null},"/query":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"joinhomeprocnopt":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"/update/csv":{"class":"org.apache.solr.handler.UpdateRequestHandler","version":"5.2.0","description":"Add
documents using XML (with XSLT), CSV, JSON, or
javabin","src":null},"joinautopracspecportal":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"autopractall2":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"allspec":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
using components:
","src":null},"/replication":{"cl

Re: Dataimport failing on SOLR 5.2

[William Bell]

Also getting:

Uncaught ReferenceError: naturalSort is not defined


On Mon, Jun 8, 2015 at 1:50 AM, William Bell  wrote:

>
>1. When I click "DataImport" in the UI on any core.. The UI just spins:
>2.
>3.
>
> http://hgsolr2devmstr:8983/solr/autosuggest/admin/mbeans?cat=QUERYHANDLER&wt=json&_=1433749812067
>
> Here is the response: 200:
>
> {"responseHeader":{"status":0,"QTime":1},"solr-mbeans":["QUERYHANDLER",{"allcondalpha":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
> using components:
> ","src":null},"autospecportal":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
> using components:
> ","src":null},"autosuggestallpracproc":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
> using components:
> ","src":null},"joinhomecondnopt":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
> using components:
> ","src":null},"allprocalpha":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
> using components:
> ","src":null},"autopayorportal":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
> using components:
> ","src":null},"joinhomespec":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
> using components:
> ","src":null},"/update/json":{"class":"org.apache.solr.handler.UpdateRequestHandler","version":"5.2.0","description":"Add
> documents using XML (with XSLT), CSV, JSON, or
> javabin","src":null},"joinhomepracspecnopt":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
> using components:
> ","src":null},"autoall2":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
> using components:
> ","src":null},"joinhomespeclocation":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
> using components:
> ","src":null},"autosuggestallpraccond":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
> using components:
> ","src":null},"/admin":{"class":"org.apache.solr.handler.admin.AdminHandlers","version":"5.2.0","description":"Register
> Standard Admin
> Handlers","src":null},"autocondportal":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
> using components:
> ","src":null},"autoeduportal":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
> using components:
> ","src":null},"/debug/dump":{"class":"org.apache.solr.handler.DumpRequestHandler","version":"5.2.0","description":"Dump
> handler
> (debug)","src":null},"/admin/mbeans":{"class":"org.apache.solr.handler.admin.SolrInfoMBeanHandler","version":"5.2.0","description":"Get
> Info (and statistics) for registered
> SolrInfoMBeans","src":null},"exactmatch2":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
> using components:
> ","src":null},"/update/json/docs":{"class":"org.apache.solr.handler.UpdateRequestHandler&

Re: Dataimport failing on SOLR 5.2

[William Bell]

Uncaught ReferenceError: naturalSort is not defined
$.ajax.success @ dataimport.js?_=5.2.0:48
jQuery.Callbacks.fire @ require.js?_=5.2.0:3126
jQuery.Callbacks.self.fireWith @ require.js?_=5.2.0:3244
done @ require.js?_=5.2.0:9482
jQuery.ajaxTransport.send.callback @ require.js?_=5.2.0:10263

On Mon, Jun 8, 2015 at 2:10 AM, William Bell  wrote:

> Also getting:
>
> Uncaught ReferenceError: naturalSort is not defined
>
>
> On Mon, Jun 8, 2015 at 1:50 AM, William Bell  wrote:
>
>>
>>1. When I click "DataImport" in the UI on any core.. The UI just
>>spins:
>>2.
>>3.
>>
>> http://hgsolr2devmstr:8983/solr/autosuggest/admin/mbeans?cat=QUERYHANDLER&wt=json&_=1433749812067
>>
>> Here is the response: 200:
>>
>> {"responseHeader":{"status":0,"QTime":1},"solr-mbeans":["QUERYHANDLER",{"allcondalpha":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>> using components:
>> ","src":null},"autospecportal":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>> using components:
>> ","src":null},"autosuggestallpracproc":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>> using components:
>> ","src":null},"joinhomecondnopt":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>> using components:
>> ","src":null},"allprocalpha":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>> using components:
>> ","src":null},"autopayorportal":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>> using components:
>> ","src":null},"joinhomespec":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>> using components:
>> ","src":null},"/update/json":{"class":"org.apache.solr.handler.UpdateRequestHandler","version":"5.2.0","description":"Add
>> documents using XML (with XSLT), CSV, JSON, or
>> javabin","src":null},"joinhomepracspecnopt":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>> using components:
>> ","src":null},"autoall2":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>> using components:
>> ","src":null},"joinhomespeclocation":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>> using components:
>> ","src":null},"autosuggestallpraccond":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>> using components:
>> ","src":null},"/admin":{"class":"org.apache.solr.handler.admin.AdminHandlers","version":"5.2.0","description":"Register
>> Standard Admin
>> Handlers","src":null},"autocondportal":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>> using components:
>> ","src":null},"autoeduportal":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>> using components:
>> ","src":null},"/debug/dump":{"class":"org.apache.solr.handler.DumpRequestHandler","version":"5.2.0","description":"Dump
>> handler
>> (debug)","src":null},"/admin/mbeans":{"class":"org.apache.solr.handl

Re: Dataimport failing on SOLR 5.2

[William Bell]

https://issues.apache.org/jira/browse/SOLR-7588

On Mon, Jun 8, 2015 at 2:11 AM, William Bell  wrote:

> Uncaught ReferenceError: naturalSort is not defined
> $.ajax.success @ dataimport.js?_=5.2.0:48
> jQuery.Callbacks.fire @ require.js?_=5.2.0:3126
> jQuery.Callbacks.self.fireWith @ require.js?_=5.2.0:3244
> done @ require.js?_=5.2.0:9482
> jQuery.ajaxTransport.send.callback @ require.js?_=5.2.0:10263
>
> On Mon, Jun 8, 2015 at 2:10 AM, William Bell  wrote:
>
>> Also getting:
>>
>> Uncaught ReferenceError: naturalSort is not defined
>>
>>
>> On Mon, Jun 8, 2015 at 1:50 AM, William Bell  wrote:
>>
>>>
>>>1. When I click "DataImport" in the UI on any core.. The UI just
>>>spins:
>>>2.
>>>3.
>>>
>>> http://hgsolr2devmstr:8983/solr/autosuggest/admin/mbeans?cat=QUERYHANDLER&wt=json&_=1433749812067
>>>
>>> Here is the response: 200:
>>>
>>> {"responseHeader":{"status":0,"QTime":1},"solr-mbeans":["QUERYHANDLER",{"allcondalpha":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>>> using components:
>>> ","src":null},"autospecportal":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>>> using components:
>>> ","src":null},"autosuggestallpracproc":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>>> using components:
>>> ","src":null},"joinhomecondnopt":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>>> using components:
>>> ","src":null},"allprocalpha":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>>> using components:
>>> ","src":null},"autopayorportal":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>>> using components:
>>> ","src":null},"joinhomespec":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>>> using components:
>>> ","src":null},"/update/json":{"class":"org.apache.solr.handler.UpdateRequestHandler","version":"5.2.0","description":"Add
>>> documents using XML (with XSLT), CSV, JSON, or
>>> javabin","src":null},"joinhomepracspecnopt":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>>> using components:
>>> ","src":null},"autoall2":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>>> using components:
>>> ","src":null},"joinhomespeclocation":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>>> using components:
>>> ","src":null},"autosuggestallpraccond":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>>> using components:
>>> ","src":null},"/admin":{"class":"org.apache.solr.handler.admin.AdminHandlers","version":"5.2.0","description":"Register
>>> Standard Admin
>>> Handlers","src":null},"autocondportal":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>>> using components:
>>> ","src":null},"autoeduportal":{"class":"org.apache.solr.handler.component.SearchHandler","version":"5.2.0","description":"Search
>>> using components:
>>

AngularJS

[William Bell]

Finding DIH issue with the new AngularJS DIH section, while indexing...

1,22613/s ?

Last Update: 22:50:50
*Indexing since 0:1:38.204*
Requests: 1, Fetched: 1,22613/s, Skipped: 0, Processed: 1,22613/s
Started: 3 minutes ago

-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076

Performance RptWithGeometrySpatialField ?

[William Bell]

Any performance implications for RptWithGeometrySpatialField ?

We use simple radius (Circle) using {!geofilt}, and MultiValued fields for
Points.

Replace it any try?

How about caching? Recommendations?


-- 
Bill Bell
billnb...@gmail.com
cell 720-256-8076