Hi,
I've found a very strange behaviour for ttf function query.
I can understand that ttf should be based on full-text query.
My query analyser is configured as follows:
When i query a term "D blooms" via
ra <u...@odoko.co.uk> wrote:
>
>
> On Wed, Sep 16, 2015, at 06:37 PM, Jie Gao wrote:
> > Hi,
> >
> >
> > I want to query a list of terms indexed and stored in multivalued string
> > field via Term Component. The term component can support exact matching
to filter).
Jie Gao,
Research Assistant,
Department of Computer Science, The University of Sheffield,
Regent Court, 211 Portobello, S1 4DP, Sheffield, UK
On 16 September 2015 at 21:04, Upayavira <u...@odoko.co.uk> wrote:
> That is, use a TextField plus a KeywordTokenizerFactory, ra
Hi,
I want to query a list of terms indexed and stored in multivalued string
field via Term Component. The term component can support exact matching and
regex based fuzzy matching. However, Is any way i can configure scheme to
do phonetic matching/query?
Thanks,
Jerry
A typo is fixed in the following query url.
On 10 September 2015 at 10:25, Jie Gao <j@sheffield.ac.uk> wrote:
> Hi,
>
> I'm wondering whether solr ttf functionQuery support (compound words)
> ngram (n>2) ?
>
> I'm using "
> http://localhost:8983/solr/c
Hi,
I'm wondering whether solr ttf functionQuery support (compound words) ngram
(n>2) ?
I'm using "
http://localhost:8983/solr/collection1/select?q=*:*=ttf(content,%22apple%20banana%22)=1"
to query total term frequency of bigram tokens in "content" field in the
whole index.
However, the result
%22apple%20banana%22>
collection1
<http://localhost:8983/solr/collection1/select?q=*:*=ttf(content,%22apple%20banana%22)=1>
/select?q=content:%22apple%20banana%22&*rows=100*".
Thanks,
Jerry
Jie Gao,
Research Assistant,
Department of Computer Science, The University of Sh
Hi,
how to parse json response from Solr Term Vector Component?
I got following json structure from response when testing Solr 5.3.0
tvComponent:
{'responseHeader': {'status': 0, 'QTime': 4}, 'response': {'docs':
[{'resourcename': 'XXX.txt', 'id': 'XXX.txt', '_version_':
1511851008560463872,
