Please let me know about your conclusion ?
i am also in same confusion.
On Thu, Nov 17, 2016 at 12:55 PM, Dorian Hoxha
wrote:
> Hi,
>
> I see that there is a new release on every lucene release. Do you always
> use the latest version since it may have bugs (ex most cassandra
> productions are ol
t; after backing up & deleting current index from dataDir.
> Also note that, adding docValue=true would increase size of index.
>
> 2)>Each node memory parameter : -Xms2g, -Xmx4g
> What is the basis choosing above memory sizes? Have you observed through
> jconsole or vis
Cluster details :
Solr Version : solr-4.10.4
No of nodes : 2 each 16 GB RAM
Node of shards : 2
Replication : 1
Each node memory parameter : -Xms2g, -Xmx4g
Collection details :
No of docs in my collection : 12.31 million
Indexed field per document : 2
Unique key field : tids
Stored filed per doc
Requesting Solr experts again to suggest some solutions to my above problem
as i am not able to solve this.
On Tue, May 12, 2015 at 11:04 AM, Naresh Yadav wrote:
> Thanks Andrew, You got my problem precisely But solutions you suggested
> may not work for me.
>
> In my API i get
aresh,
>
> Couldn't you could just model this as an OR query since your requirement
> is at least one (but can be more than one), ie:
>
> tags:T1 tags:T2 tags:T3
>
> -sujit
>
>
> On Mon, May 11, 2015 at 4:14 AM, Naresh Yadav
> wrote:
>
> > Hi al
Hi all,
Also asked this here : http://stackoverflow.com/questions/30166116
For example i have SOLR docs in which tags field is indexed :
Doc1 -> tags:T1 T2
Doc2 -> tags:T1 T3
Doc3 -> tags:T1 T4
Doc4 -> tags:T1 T2 T3
Query1 : get all docs with "tags:T1 AND tags:T3" then it works and will
give
Setup1 i.e 2 minutes.
Actually first 50 thousand request it self is taking about a minute. May be
i would need to see other things as pagination seems working better now.
thanks for giving valuable suggestions.
On Mon, Jan 19, 2015 at 11:20 AM, Naresh Yadav wrote:
> Toke, won't be abl
For
> the next batch, limit it to id > last_id and get the first 50k docs (don't
> use start= for paging). This scales much better when scanning a large
> result set; you'll get constant time across the whole set instead of having
> it increase as you page deeper.
>
> -
ional units in post.
Thanks
Naresh
On Sun, Jan 18, 2015 at 4:19 PM, Toke Eskildsen
wrote:
> Naresh Yadav [nyadav@gmail.com] wrote:
> > In both setups, we are reading in batches of 50k and each batch taking
> > Setup1 : approx 7 seconds and for completing all batches of total 1
batch size also 10k, 1lakh but no gain in total time taken
in Setup2.
Thanks
Naresh
On Sun, Jan 18, 2015 at 6:45 AM, Andrew Butkus <
andrew.but...@c6-intelligence.com> wrote:
> &shard.info=true
>
> Sent from my iPhone
>
> > On 17 Jan 2015, at 04:23, Naresh Yadav wrote
Hi all,
We have single solr index with 3 fixed fields(on of field is tokenized with
space) and rest dynamic fields(string fields in range of 10-20).
Current size of index is 2 GB with around 12 lakh docs and solr
nodes are of 4 core, 16 gb ram linux machines.
Writes performance is good then we t
ing used all over the place and it is fast. I suggest you looks for
> faceting improvements.
>
> Ahmet
>
>
>
> On Friday, January 16, 2015 11:17 AM, Naresh Yadav
> wrote:
> I tried facetting also but not worked smoothly for me. Case i had mentioned
> in email is dummy
y with facet component. Example :
> facet=true&facet.field=tenant_pool&q=type:1
>
> Please see more here :
> https://cwiki.apache.org/confluence/display/solr/Faceting
>
> happy faceting,
> ahmet
>
>
>
> On Friday, January 16, 2015 10:13 AM, Naresh Yadav
> wrote:
lued. P.S. Don't get confused with
> TextField type, for example it could create single token when used with
> keyword tokenizer.
>
> Ahmet
>
> On Friday, January 16, 2015 4:43 AM, Naresh Yadav
> wrote:
> Hi ahmet,
>
> If you observe output ngroups is 1 and returnin
orrect, what is the problem here?
>
> If you want to see more than one document per group, there is a parameter
> for that which defaults to 1.
>
> Ahmet
>
>
>
> On Thursday, January 15, 2015 9:02 AM, Naresh Yadav
> wrote:
> Hi all,
>
> I had done following
as my problem is changed completely from first post so i had created new
thread for that.
On Wed, Jan 14, 2015 at 7:31 PM, Naresh Yadav wrote:
> just wanted to share schema and results for same :
>
> solr version : 4.6.1
> Schema : http://www.imagesup.net/?di=10142124357616
>
Hi all,
I had done following configuration to test Solr grouping concept.
solr version : 4.6.1 (tried in latest version 4.10.3 also)
Schema : http://www.imagesup.net/?di=10142124357616
Solrj code to insert docs :http://www.imagesup.net/?di=10142124381116
Response Group's : http://www.images
Please help me on this problem where no of groups are not matching with no
of terms which is expected behaviour acc to me.
Please give direction on this problem.
On Wed, Jan 14, 2015 at 5:24 PM, Naresh Yadav wrote:
> I tried what you said also appended group.ngroups=true and got same result
&g
I tried what you said also appended group.ngroups=true and got same result
not expected onengroups coming is 1.
i am on solr-4.6.1 single machine default setup.
On Wed, Jan 14, 2015 at 4:43 PM, Norgorn wrote:
> Can u get raw SOLR response?
>
> For me grouping works exactly the way u expect i
#x27;re completely different beasts.
>
> your original question was:
> "Please guide me how i can tell solr not to tokenize stored field to decide
> unique groups.."
>
> Simply declare the field type you care about as a "string" type in
> schema.xml. The use a
mment is, just start by making the field you
> want
> to group on be
> stored="false" indexed="true" type="string"
>
> Best,
> Erick
>
> On Tue, Jan 13, 2015 at 5:09 AM, Naresh Yadav
> wrote:
> > Hi jack,
> >
> > Thanks for replyi
n Tue, Jan 13, 2015 at 7:33 AM, Naresh Yadav
> wrote:
>
> > *Schema :*
> >
> >
> > *Code :*
> > SolrQuery q = new SolrQuery().setQuery("*:*");
> > q.set(GroupParams.GROUP, true);
> > q.set(GroupParams.GROUP_FIELD, "tenant_pool");
>
*Schema :*
*Code :*
SolrQuery q = new SolrQuery().setQuery("*:*");
q.set(GroupParams.GROUP, true);
q.set(GroupParams.GROUP_FIELD, "tenant_pool");
*Data :*
"tenant_pool" : "Baroda Farms"
"tenant_pool" : "Ketty Farms"
*Output coming :*
groupValue=Farms, docs=2
*Expected Output :*
groupValue=Baro
23 matches
Mail list logo
