date:20110718

Re: random record from solr server

2011-07-18 Thread Ahmet Arslan

> How can I get random 100 record from last two days record
> from solr server.
> 
> I am using solr 3.1

Hello, add this random field definition to you schema.xml



Generate some seed value ( e.g. 125) at query time,

and issue a query something like this:

q:add_date[NOW-2DAYS TO *]&sort=random_125&start=0&rows=100

If you use different seed values each time you will get random 100 record in 
each request. I assume you have date field to store add date or similar.

Re: SolrJ Collapsable Query Fails

2011-07-18 Thread Kurt Sultana

Hi,

Thanks for the code, snippet, it was very useful, however, can you please
include a very small description of certain unknown variables such as
'groupedInfo', 'ResultItem', 'searcher', 'fields' and the method
'solrDocumentToResultItem'?

Thanks

On Sat, Jul 16, 2011 at 3:36 PM, Kurt Sultana  wrote:

> > Thanks for the information. However, I still have one more
> > problem. I am
> > iterating over the values of the NamedList. I have 2
> > values, one
> > being 'responseHeader' and the other one being 'grouped'. I
> > would like to
> > access some information stored within the grouped section,
> > which has
> > data structured like so:
> >
> >
> grouped={attr_directory={matches=4,groups=[{groupValue=C:\Users\rvassallo\Desktop\Index,doclist={numFound=2,start=0,docs=[SolrDocument[{attr_meta=[Author,
> > kcook, Last-Modified, 2011-03-02T14:14:18Z...
> >
> > With the 'get("group")' method I am only able to access the
> > entire
> > '{attr_directory={matches=4,g...' section. Is there some
> > functionality which
> > allows me to get other data? Something like this for
> > instance:
> > 'get("group.matches")' or maybe
> > 'get(group.attr_directory.matches)' (which
> > will yield the value of 4), or do I need to process the
> > String that the
> > 'get("...")' returns to get what I need?
> >
> > Thanks :)
>
> I think accessing the relevant portion in a NamedList is troublesome. I
> suggest you to look at existing codes in solrJ. e.g. How facet info is
> extracted from NamedList.
>
> I am sending you the piece of code that I used to access grouped info.
> Hopefully It can give you some idea.
>
>  NamedList signature = (NamedList) groupedInfo.get("attr_directory");
>
>if (signature == null) return new ArrayList(0);
>
>matches.append(signature.get("matches"));
>
>
>@SuppressWarnings("unchecked")
>ArrayList groups = (ArrayList)
> signature.get("groups");
>
>ArrayList<> resultItems = new ArrayList<>(groups.size());
>
>StringBuilder builder = new StringBuilder();
>
>
>for (NamedList res : groups) {
>
>  ResultItem resultItem = null;
>
>  String hash = null;
>  Integer found = null;
>  for (int i = 0; i < res.size(); i++) {
>String n = res.getName(i);
>
>Object o = res.getVal(i);
>
>if ("groupValue".equals(n)) {
>  hash = (String) o;
>} else if ("doclist".equals(n)) {
>  DocList docList = (DocList) o;
>  found = docList.matches();
>
>  try {
>final SolrDocumentList list =
> SolrPluginUtils.docListToSolrDocumentList(docList, searcher, fields, null);
>builder.setLength(0);
>
>if (list.size() > 0)
>  resultItem = solrDocumentToResultItem(list.get(0), debug);
>
>for (final SolrDocument document : list)
>  builder.append(document.getFieldValue("id")).append(',');
>
>
>  } catch (final IOException e) {
>LOG.error("Unexpected Error", e);
>  }
>}
>
>
>  }
>
>  if (found != null && found > 1 && resultItem != null) {
>resultItem.setHash(hash);
>resultItem.setFound(found);
>builder.setLength(builder.length() - 1);
>resultItem.setId(builder.toString());
>  }
>
>  // debug
>
>
>  resultItems.add(resultItem);
>}
>
>return resultItems;
>
>

Re: Fuzzy Query Param

2011-07-18 Thread steffen_kmt

entdeveloper wrote:
> 
> I'm using Solr trunk. 
> 

Hi!

I'm using solr 3.1.0 and the feature is not implemented. 
When I search for a word with e.g. ~2 the "~2" is interpreted as part of the
search string. 
Where can I get the trunk version? Is it a stable version or just for
testing purposes?

thanks a lot,

steffen

--
View this message in context: 
http://lucene.472066.n3.nabble.com/Fuzzy-Query-Param-tp3120235p3178565.html
Sent from the Solr - User mailing list archive at Nabble.com.

LockObtainFailedException and open finalizing IndexWriters

2011-07-18 Thread Michael Kuhlmann

Hi,

we are running Solr 3.2.0 on Jetty for a web application. Since we just
went online and are still in beta tests, we don't have very much load on
our servers (indeed, they're currently much oversized for the current
usage), and our index size on file system ist just 1.1 MB.

We have one dedicated Solr instance for updates, and two replicated
read-only servers for requests. The update server gets filled by three
different Java web servers, each has a distinct Quartz job for its
updates. Every such Quartz job takes all collected updates, sends them
via Solrj's addBeans() method, and from time to time, they send an
additional commit() after that. Each update job has a
CommonHTTPSolrServer instance, which is a Spring controlled singleton.

We already had LockObtainFailedExceptions before, raising every few
days. Sometimes, we had such an exception before:
org.apache.solr.common.SolrException: java.io.IOException: directory
'/data/solr/data/index' exists and is a directory, but cannot be listed:
list() returned null

This looks like if there were no more file handles from the operating
system. This is strange, since the only index directory never had more
than 100 files, if ever. However, we raised ulimit -n from 1024 to 4096,
and reduced mergeFactor from 10 to 5, which firsted helped us with our
problem. Until yesterday.

Again, we had this:
org.apache.lucene.store.LockObtainFailedException: Lock obtain timed
out: SimpleFSLock@solr/main/data/index/write.lockat
org.apache.lucene.store.Lock.obtain(Lock.java:84)at
org.apache.lucene.index.IndexWriter.(IndexWriter.java:1114)at
org.apache.solr.update.SolrIndexWriter.(SolrIndexWriter.java:83)
at
org.apache.solr.update.UpdateHandler.createMainIndexWriter(UpdateHandler.java:101)
at
org.apache.solr.update.DirectUpdateHandler2.openWriter(DirectUpdateHandler2.java:174)
at
org.apache.solr.update.DirectUpdateHandler2.addDoc(DirectUpdateHandler2.java:222)
at
org.apache.solr.update.processor.RunUpdateProcessor.processAdd(RunUpdateProcessorFactory.java:61)

When we deleted the write.lock file without restarting Solr, several
hours later we had 441 same log entries:

Jul 18, 2011 7:20:29 AM org.apache.solr.update.SolrIndexWriter finalize
SEVERE: SolrIndexWriter was not closed prior to finalize(), indicates a
bug -- POSSIBLE RESOURCE LEAK!!!

Wow, if there really were 441 open IndexWriters trying to access the
index directory, it's no wonder that there will be Lock timeouts sooner
or later! However, I have no clue why there are so many IndexWriters
opened and never closed. The only accessing Solr instances are pure Java
applications using Solrj. Each application only has one SolrServer
instance - and even of not, this shouldn't harm, AFAIK. The update job
is started every five seconds. The installation is a pure 3.2.0 Solr,
without additional jars. And all jars are of the correct revision. The
solrconfig.xml is based on the example configuration, with nothing
special. We currently don't have any own extensions running. There is
absolutely only one jetty instance running on the machine. And I checked
the solr.xml, it's only one core defined, and we don't do any additional
core administration.

67 matches

Mail list logo