On Wed, Apr 25, 2012 at 8:18 AM, prakash_ajp wrote:
> Is it true that faceting is case sensitive? That would be disastrous for
> our
> requirement :(
>
>
it depends on your schema definition: if you lower case your tokens both
for index and query sides, the faceting should not be case sensitive.
Is it true that faceting is case sensitive? That would be disastrous for our
requirement :(
--
View this message in context:
http://lucene.472066.n3.nabble.com/Auto-suggest-on-indexed-file-content-filtered-based-on-user-tp3934565p3937370.html
Sent from the Solr - User mailing list archive at Nabb
The first one may not work because the number of users can be big. Besides,
the users can simply register themselves and start using it. It won't work
if an admin has to intervene in the registration process.
The second could work I guess. But the problem would be data duplication as
users might a
Another option is to use faceting (via the facet.prefix param) for your
auto-suggest. It's not as fast and scalable as using one of the
Suggester implementations, but it does allow arbitrary fq parameters to
be included in the request to limit the results.
http://wiki.apache.org/solr/SimpleFa
I don't know if there is a really good solution here. The problem is that
suggester (and the trunk FST version) simply traverse the terms in
the index. there's not even a real concept of those terms belonging to
any document. Since your security level is on a document basis, that
makes things hard.
yes only spellcheck indexed build field is for suggest query
I believe, filtering a documents on search handler using fq parameter and spell
suggest are two part we are discussing here.
lets say you have field for spellcheck - used to build spell dictionary
using copyField for populating a spe
I read on a couple of other web pages that fq is not supported for suggester.
I even tried the query and it doesn't help. My understanding was, when the
suggest (spellcheck) index is built, only the field chosen is considered for
queries and the other fields from the main index are not available fo
Auto suggest on indexed file content filtered based on user
Right now, the query is a very simple one, something like q=text. Basically, it
would return ['textview', 'textviewer', ..]
But the issue is, the 'textviewer' could be from a file that is out of bounds
fo
On Apr 24, 2012, at 9:37 PM, prakash_ajp wrote:
> Right now, the query is a very simple one, something like q=text. Basically,
> it would return ['textview', 'textviewer', ..]
hmm, so you're using default query field
>
> But the issue is, the 'textviewer' could be from a file that is out of
>
Right now, the query is a very simple one, something like q=text. Basically,
it would return ['textview', 'textviewer', ..]
But the issue is, the 'textviewer' could be from a file that is out of
bounds for this user. So, ultimately I would like to include the userName in
the query. As mentioned ea
can you please share a sample query?
-Jeevanandam
On 24-04-2012 1:49 pm, prakash_ajp wrote:
I am trying to implement an auto-suggest feature. The search feature
already
exists and searches on file content in user's allotted workspace.
The following is from my schema that will be used for se
11 matches
Mail list logo
