RE: indexing documents (or pieces of a document) by access controls

Hello, Given the requirement to break down a document into separately controlled pieces, I'd create a servlet that fronts the Solr servlet and handles this conversion. I could think of ways to do it using Solr, but they feel like unnatural acts. As a general comment on ACLs, one

RE: indexing documents (or pieces of a document) by access controls

Hello, Hi And about the fields, if they are/aren't going to be present on the responses based on the user group, you can do it in many different ways (using XML transformation to remove the undesirable fields, implementing your own RequestHandler able to process your group

Can we change structure of add command?

Hi Friends, I am new to Solr technology. I want to do searching for xml documents. In source distribution examples of solr, we have same structure of XML documents i.e. add doc field/field field/field ... /doc /add Can we change this structure of posting xml

Re: Multi-language indexing and searching

Hi Hoss One bad thing in having fields specific for your language (in my point of view) is that you will have to re-index your content when you add a new language (some will need to start with one language and in future will have others added). But OK, let's say the indexing is done. So using

Re: Can we change structure of add command?

Vika - no, Solr's add-document XML syntax is not flexible in the way you've described. Solr fronts a Lucene index. A Lucene index is made up of Documents which have Fields. Fields are a flat structure, not hierarchical. The trick to leveraging Solr and Lucene successfully is in the

Unfriendly Weblogic

Hi guys, I've tried deploying Solr on Weblogic and am gettting the following error in my console trace: 13-Jun-2007 15:37:35 org.apache.solr.core.Config getInstanceDir INFO: using system property solr.home: D:/apache-solr-1.2.0/example/solr/ 13-Jun-2007 15:37:35 org.apache.solr.core.Config

Re: Unfriendly Weblogic

Which version of Weblogic are you trying? Some old versions have a wrong javax.servlet.Filter interface definition... Regards, Daniel On 13/6/07 15:59, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi guys, I've tried deploying Solr on Weblogic and am gettting the following error in my

Re: Unfriendly Weblogic

sorry - I'm using weblogic 9.2 Daniel Alheiros [EMAIL PROTECTED] 13/06/2007 16:05 Please respond to solr-user To: solr-user@lucene.apache.org cc: Subject:Re: Unfriendly Weblogic Which version of Weblogic are you trying? Some old versions have a

Re: Unfriendly Weblogic

Sorry, probably it's not the case then... On 13/6/07 16:07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: sorry - I'm using weblogic 9.2 Daniel Alheiros [EMAIL PROTECTED] 13/06/2007 16:05 Please respond to solr-user To: solr-user@lucene.apache.org

problems getting data into solr index

Hello everyone I'm running solr1.2 and Jetty, I'm having problems looping through a mysql database with python and putting the data into the solr index. Here's the error UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 369: ordinal not in range(128) I think that means that

Re: Compass vs Solr

If your question is about scaling only, I'd put my money on Solr when compared to Compass+Lucene if you are looking at the OO(T?)B offering. Check the Solr Wiki for Master/Slave information. If you go with Compass+Lucene, you'll need to do implement something like that yourself. Otis --

Re: problems getting data into solr index

On 6/13/07, vanderkerkoff [EMAIL PROTECTED] wrote: I'm running solr1.2 and Jetty, I'm having problems looping through a mysql database with python and putting the data into the solr index. Here's the error UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 369: ordinal not in

Re: problems getting data into solr index

UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 369: ordinal not in range(128) What character is at position 369? make sure it is valid unicode... Is there a simple way to tell solr to accept UTF8 characters? Solr can accept UTF8 characters... check the

Re: Compass vs Solr

compass is nice: you install it and it just works. I was totally impressed. Can anyone suggest which one would perform/scale well Compass or Solr? It depends on what your app looks like. If you need to update the index from multiple computers at the same time (load balancing) - solr is

Re: Unfriendly Weblogic

hmmm... the INFO log suggests it has found my solr.solr.home argument ok. I don't know how readable the whole stack is but I've included it below. Have I missed a step in the setup? The only steps to deploy Solr I've taken are: 1) Add -Dsolr.solr.home=D:/apache-solr-1.2.0/example/solr as a JVM

Re: Unfriendly Weblogic

: hmmm... the INFO log suggests it has found my solr.solr.home argument ok. it's more a question of wether or not there were any errors when trying to load any classes needed to parse your configs (either because they are staticly refered to, or because they are loaded by reflection based on

Delete entire index

Hi, Is there a way to have Solr completely remove the current index? deleteAll/ ? We're still in development and so our schema is wavering. Anytime we make a change and want to re-index we first have to: stop tomcat (or the solr webapp) manually remove the data/index restart tomcat (or

Re: Delete entire index

Matt, I could be wrong, but I think you can send a delete by query syntax: deletequery*:*/query/delete -- Thiago Jackiw acts_as_solr = http://acts-as-solr.railsfreaks.com On 6/13/07, Matt Mitchell [EMAIL PROTECTED] wrote: Hi, Is there a way to have Solr completely remove the current index?

Re: Delete entire index

I agree... and the fix really belongs at the Lucene level: https://issues.apache.org/jira/browse/LUCENE-932 -Yonik On 6/13/07, Matt Mitchell [EMAIL PROTECTED] wrote: Hi, Is there a way to have Solr completely remove the current index? deleteAll/ ? We're still in development and so our schema

sort throws exception

I'm using DisMaxRequestHandler and my queries seem to work fine. I intended to add an option to sort on a date type field. However, the moment I add sort, I get an exception (listed at the bottom of this email.) Then I tried with sort=score and the exception still happens. I'm sure it's due to my

Re: sort throws exception

Try sort=score desc Looks like we need some better error checking and more friendly error messages. -Yonik On 6/13/07, Jack L [EMAIL PROTECTED] wrote: I'm using DisMaxRequestHandler and my queries seem to work fine. I intended to add an option to sort on a date type field. However, the moment

Re: Delete entire index

: I could be wrong, but I think you can send a delete by query syntax: : deletequery*:*/query/delete correct ... deleting *:* followed by doing an optimize/ should be functionally equivilent to stoping the servlet container, removing the directory and starting the sorl container ... but it won't

Re: sort throws exception

: However, the moment I add sort, I get an exception (listed at the : bottom of this email.) Then I tried with sort=score and the : exception still happens. I'm sure it's due to my ignorance because : sort must be a well tested parameter. I wonder what I'm doing wrong? :

Re: Delete entire index

: correct ... deleting *:* followed by doing an optimize/ should be : functionally equivilent to stoping the servlet container, removing the : directory and starting the sorl container ... but it won't be quite as : efficient. : : Actually, it's not quite equivalent if there was a schema

Re: Delete entire index

On 6/13/07, Chris Hostetter [EMAIL PROTECTED] wrote: : I could be wrong, but I think you can send a delete by query syntax: : deletequery*:*/query/delete correct ... deleting *:* followed by doing an optimize/ should be functionally equivilent to stoping the servlet container, removing the

Re: Delete entire index

On 6/13/07, Chris Hostetter [EMAIL PROTECTED] wrote: : correct ... deleting *:* followed by doing an optimize/ should be : functionally equivilent to stoping the servlet container, removing the : directory and starting the sorl container ... but it won't be quite as : efficient. : :

Re: indexing documents (or pieces of a document) by access controls

Hello, With all do respect, I really think the problem is largely underestimated here, and is far more complex then these suggestions...unless we are talking about 100.000 documents, couple of users, and updating ones a day. If you want millions of documents, facetted authorized

Re: Delete entire index

: : Actually, it's not quite equivalent if there was a schema change. : There are some sticky field properties that are per-segment global. : For example, if you added omitNorms=true to a field, then did Hmmm... I thought the optimize would take care of that? Oh yes, sorry, I was thinking

Re: Delete entire index

On 6/13/07, Ryan McKinley [EMAIL PROTECTED] wrote: : : Actually, it's not quite equivalent if there was a schema change. : There are some sticky field properties that are per-segment global. : For example, if you added omitNorms=true to a field, then did Hmmm... I thought the optimize

Re[2]: sort throws exception

Hello Chris, I'm using version 1.1. If I'm only using 1.1 features, should I still try 1.2 for other improvements such as stability, error handling, etc.? -- Best regards, Jack Wednesday, June 13, 2007, 12:23:35 PM, you wrote: : However, the moment I add sort, I get an exception (listed at

Re: sort throws exception

Jack L wrote: Hello Chris, I'm using version 1.1. If I'm only using 1.1 features, should I still try 1.2 for other improvements such as stability, error handling, etc.? If you can upgrade, it is highly recommended. There are lots of little annoying fixes included in 1.2 -- in addition to

Update to SolrSharp

Solrsharp has been validated against the Solr 1.2 release. Validation was made using the example application that's available with the Solrsharp code against a default example index with the Solr 1.2 released bits. - The source code for Solrsharp is now accessible via subversion. Many thanks

Re: Update to SolrSharp

Hello Jeff, Thank you for posting Solrsharp. I just check it out and it looks like projects (src\SolrSharp.csproj , example\Example.csproj) are missing from VS solution. Thank you, Michael - Original Message - From: Jeff Rodenburg [EMAIL PROTECTED] To: solr-user@lucene.apache.org

Re: DisMax request handler doesn't work with stopwords?

I'm having the same issues. We are using Dismax, with a stopword list. Currently we are having customers typing in model ipod, we added model to the stopwords list and tested with the standard handler..works fine, but not with dismax (MM = 3lt;-1 5lt;-2 6lt;90%). When i comment out MM, it works.