Please any one can help me on this
Rgds
AJ
On 23-May-2012, at 14:37, Jens Grivolla wrote:
> So are you even doing text search in Solr at all, or just using it as a
> key-value store?
>
> If the latter, do you have your schema configured so
> that only the search_id field is indexed (with a ke
Jens,
Yes we are doing text search.
My question to all is, the approach of creating cores for each user is a
good idea?
AJ
On Wed, May 23, 2012 at 2:37 PM, Jens Grivolla wrote:
> So are you even doing text search in Solr at all, or just using it as a
> key-value store?
>
> If the latter, do y
So are you even doing text search in Solr at all, or just using it as a
key-value store?
If the latter, do you have your schema configured so
that only the search_id field is indexed (with a keyword tokenizer) and
everything else only stored? Also, are you sure that Solr is the best
option as a
Awaiting for suggestions.
On Wed, May 23, 2012 at 8:04 AM, Amit Jha wrote:
> Hi,
>
> Thanks for your advice.
> It is basically a meta search application. Users can perform a search on N
> number of data sources at a time. We broadcast Parallel search to each
> selected data sources and write da
Hi,
Thanks for your advice.
It is basically a meta search application. Users can perform a search on N
number of data sources at a time. We broadcast Parallel search to each
selected data sources and write data to solr using custom build API(API and
solr are deployed on separate machine API jo
It would help if you provide your use case. What are you indexing for each
user and why would you need a separate core for indexing each user? How do
you decide schema for each user? It might be better to describe your use
case and desired results. People on the list will be able to advice on the
b
Hi,
Could please tell me what do you mean by filter data by users? I would like
to know is there real problem creating a core for a user. ie. resource
utilization, cpu usage etc.
AJ
On Tue, May 22, 2012 at 4:39 PM, findbestopensource <
findbestopensou...@gmail.com> wrote:
> Having cores per use
Having cores per user is not good idea. The count is too high. Keep
everything in single core. You could filter the data based on user name or
user id.
Regards
Aditya
www.findbestopensource.com
On Tue, May 22, 2012 at 2:29 PM, Shanu Jha wrote:
> Hi all,
>
> greetings from my end. This is my f
Hi,
Paul and Shalin will know about this. What I'm seeing looks a lot like what
Walter reported in March:
* http://markmail.org/thread/dfsj7hqi5buzhd6n
And this commit from Paul seems possibly related:
* http://markmail.org/message/cjvjffrfszlku3ri
...because of things like:
-cores =
I too am using 1.3. They way you specified shards is correct.
For instance, I normally make the request to core0, and in the shards
parameter, I put the addresses of both core0 and core1. I am using Tomcat
though, so that may be different...
Is there anything in the logs that strikes you as odd
Thanks for the reply ahammad, that helps. Are you specifying them both in a
URL, or in the localhost:8983/solr/core0,localhost:8983/solr/core1 like
I have?
I should add that I now have two indices that have different data in them.
That is to say the ids are unique across both shards and I am sti
I have a multicore setup as well, and when I query something, I do it through
core0, then specify both core0 and core1 ins the "shards" parameter.
However, I don't have identical indicies. The results I get back are
basically and addition of both cores' results.
Good luck, please reply to this m
I am still trying to figure this out... I am thinking maybe I have the shards
setup wrong? If I have core0 and core1 with indices, and then I run the
query on core0, specifying shards of core0 and core1. Is this how I should
be doing it? Or should I have another core just to specify the other shar
- Original Message
> From: Chris Hostetter
> To: solr-user@lucene.apache.org
> Sent: Tuesday, April 7, 2009 5:41:48 PM
> Subject: Re: Multicore Solr not showing Cache Stats
>
>
> : - Going to http://localhost:8983/core1/admin/stats.jsp#cache shows a
> : nearly em
Not in this case. I literally copied the same index to the two shards, in my
non-test environment they will be unique however. If that is the issue,
wouldn't it lead to the number of results always being 793 in that case? 379
is less than either of the indices contain.
markrmiller wrote:
>
> D
Do you have unique ids across shards?
--
- Mark
http://www.lucidimagination.com
KennyN wrote:
I have a two core multicore setup which currently has identical indices (just
for testing, they will have different data when i deploy the system). I
based this off the example, so core0 and core1. I
: - Going to http://localhost:8983/core1/admin/stats.jsp#cache shows a
: nearly empty Cache section. The only cache that shows up there is
: fieldValueCache (which is really commented out in solrconfig.xml, but
: Solr creates it anyway, which is normal). All other caches are missing.
:
: Any
check now. Should be fixed in trunk
On Aug 13, 2008, at 3:05 PM, Doug Steigerwald wrote:
I checked out the trunk about 2 hours ago. Was the last commit on
the 10th supposed to fix this (r684606)?
On Aug 13, 2008, at 3:00 PM, Ryan McKinley wrote:
check a recent version, this issue should
aaah -- I see, we need the same error logic for SolrUpdateServlet as
we added for SolrServlet.
I'll fix in one sec.
Thanks
ryan
On Aug 13, 2008, at 3:05 PM, Doug Steigerwald wrote:
I checked out the trunk about 2 hours ago. Was the last commit on
the 10th supposed to fix this (r684606)?
I checked out the trunk about 2 hours ago. Was the last commit on the
10th supposed to fix this (r684606)?
On Aug 13, 2008, at 3:00 PM, Ryan McKinley wrote:
check a recent version, this issue should have been fixed in:
https://issues.apache.org/jira/browse/SOLR-545
On Aug 13, 2008, at 2:22
check a recent version, this issue should have been fixed in:
https://issues.apache.org/jira/browse/SOLR-545
On Aug 13, 2008, at 2:22 PM, Doug Steigerwald wrote:
Yeah, that's the problem. Not having the core in the URL you're
posting to shouldn't update any core, but it does.
Doug
On Aug
Yeah, that's the problem. Not having the core in the URL you're
posting to shouldn't update any core, but it does.
Doug
On Aug 13, 2008, at 2:10 PM, Alok K. Dhir wrote:
you need to add the core to your call -- post to
http://localhost:8983/solr/coreX/update
On Aug 13, 2008, at 1:58 PM, Do
you need to add the core to your call -- post to
http://localhost:8983/solr/coreX/update
On Aug 13, 2008, at 1:58 PM, Doug Steigerwald wrote:
I've got two cores (core{0|1}) both using the provided example
schema (example/solr/conf/schema.xml).
Posting to http://localhost:8983/solr/update ad
23 matches
Mail list logo
