Sorry, I've been a bit unfocused from this list for a bit. When I was
working with the APTF code I rewrote a big chunk of it and didn't include
the inclusion of the original tokens as I didn't need it at the time. That
feature could easily be added back in. I will see if I can find a bit of
time fo
he same number as the last word in the matched series?
>
> BTW, i looked at your code re this. It is quite informative to a
> newbie. Thanks!
>
>
> On 3/19/2015 11:38 AM, James Strassburg [via Lucene] wrote:
>
> Sorry, I've been a bit unfocused from this
Hello,
I've been using auto-phrasing. I believe it was my company's query to
LucidWorks that got that initial implementation created.
In working with it I found a few issues and forked the repo and simplified
some code (where I didn't need features) and expanded the testing quite a
bit. I've got m
Also, Shamik:
I believe you need to configure the AutoPhrasingTokenFilterFactory in your
query analyzer for your text_autophrase field type.
JiM
On Fri, Dec 12, 2014 at 2:39 PM, James Strassburg
wrote:
>
> Hello,
>
> I've been using auto-phrasing. I believe it was my c
I'm on 4.8.1
On Fri, Dec 12, 2014 at 3:11 PM, shamik wrote:
>
> Jim,
>
> Thanks for your response. I've tried including
> AutoPhrasingTokenFilterFactory as part of the query analyzer, but didn't
> make any difference.
>
> positionIncrementGap="100">
>
>
Yes, actually that was one of the bugs I fixed so that we could
replaceWhitespaceWith nothing.
On Fri, Dec 12, 2014 at 3:34 PM, Ted Sullivan
wrote:
>
> Hi Shamik:
>
> One thing that might help is to use the "replaceWhitespaceWith" parameter
> of
> the QParserPlugin and in your index-time Autophra
Yes, I'll submit a pull-request back to the LucidWorks github. For the
specific replaceWhitespaceWith nothing issue look at my changesets:
https://github.com/jstrassburg/auto-phrase-tokenfilter/commit/a9450f2500d864539b3e5632c6cd47b283f3a481
and
https://github.com/jstrassburg/auto-phrase-tokenfilt
Hello,
We're creating a SolrCloud in AWS and attempting to use autoscaling to add
replicas during nodeAdded/nodeLost. This was working fine for us until we
started creating collections specifying core properties (e.g.
/solr/admin/collections?action=CREATE&property.synonyms_datasource=REDACTED).
It
toscaling actions such as ComputePlanAction to add custom
> core properties to any add replica or move replica command. That is
> probably worth another Jira as well.
>
>
> On Wed, Sep 5, 2018 at 11:54 PM James Strassburg
> wrote:
>
> > Hello,
> >
> > We're cr
revented us
from validating the Config API (unless we had something configured wrong).
Moving on to SOLR_OPTS to see if that will work but it is undesirable since
the admin UI will display the settings (some of them sensitive).
JiM
On Thu, Sep 6, 2018 at 8:24 AM James Strassburg
wrote:
>
10 matches
Mail list logo
