lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sara hajili <hajili.s...@gmail.com>
Subject Re: plz help me
Date Tue, 01 Sep 2015 12:07:47 GMT
and another question is:
my docs are persian and i use text_fa for fieldType but i wanna to have a
persian textfield that handle search problem such as stemming.
word distance,synonyms etc
like english types.
as i said i handle "میخواهم " and "خواستن"  and so on.
can you suggest me a fieldtype for handle this issues in persian field.
tnx

On Tue, Sep 1, 2015 at 3:16 AM, sara hajili <hajili.sara@gmail.com> wrote:

> i'm really confused:|
> i'm really anxious about cost of update like count.
> and as you said:
> <field name="like_count" type="int" indexed="true" stored="true"
> docValues="true"/>
> you indexed like_count field .and i think it cost alot to update and index
> again docs.
> because like count change more and more
> so isn't better to indede="false" that this field name??!!
>
> On Tue, Sep 1, 2015 at 3:08 AM, Upayavira <uv@odoko.co.uk> wrote:
>
>> you don't need to use a dynamic field, just a normal field will work for
>> you. But, you *will* want to index it, and you may benefit from
>> docValues, so:
>>
>> <field name="like_count" type="int" indexed="true" stored="true"
>> docValues="true"/>
>>
>> Upayavira
>>
>> On Tue, Sep 1, 2015, at 10:59 AM, sara hajili wrote:
>> > my solr version is 5.2.1
>> > i have a question.
>> > if i create 2 core .one for post and one for like . i must index like
>> > count?
>> > i mean in schema for like core i must write:
>> > <dynamicField name="like_count"  type="int"    indexed="false"
>> > stored="true"/>
>> >
>> > am i true?
>> >
>> > On Tue, Sep 1, 2015 at 2:42 AM, Upayavira <uv@odoko.co.uk> wrote:
>> >
>> > > So you want to be able to sort by the "number of likes" value for a
>> > > post?
>> > >
>> > > What version of Solr are you using? How many posts do you have?
>> > >
>> > > There's a neat feature in Solr 5.2.1 (I'm pretty sure it is there, not
>> > > 5.3) called score joins. Using that you can have two cores, one
>> > > containing your posts, and another containing your likes.
>> > >
>> > > You cannot *sort* on these values, but you can include your likes into
>> > > the score, which might even be better.
>> > >
>> > > If this sounds good, I can dig up some syntax for such a query.
>> > >
>> > > Upayavira
>> > >
>> > > On Tue, Sep 1, 2015, at 10:36 AM, sara hajili wrote:
>> > > > hi.
>> > > > at first i.m sorry for my bad english!
>> > > > i have a social app.i want to use solr for searching in this app.
>> > > > i have many document (in my case people text that posted on my
>> social
>> > > > app).
>> > > > and i indexed this.
>> > > > but i'm have 1 issue and it is :
>> > > >
>> > > > i have very doc(post) and they have a property "like" is it  good
>> > > > approach
>> > > > to index like count (people can like eachother post in my social
>> app)?
>> > > > likecount change more and more in one day.(so as i know it must be
>> set
>> > > > dynamic field)
>> > > > and if i indexed it ,i think  it costs alot , to update and index
>> > > > likecount
>> > > > more and more even i use bach update.
>> > > > so is it approach to didn't index one field in solr but i could
>> sort my
>> > > > search result according to that unindexed field?
>> > > >
>> > > > tnx
>> > >
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message