[jira] Updated: (SOLR-362) bundle junit with solr
[ https://issues.apache.org/jira/browse/SOLR-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Scherler updated SOLR-362: --- Attachment: junit.include.diff junit-4.3.jar Patch to bundle junit with solr. bundle junit with solr -- Key: SOLR-362 URL: https://issues.apache.org/jira/browse/SOLR-362 Project: Solr Issue Type: Improvement Reporter: Thorsten Scherler Attachments: junit-4.3.jar, junit.include.diff http://marc.info/?t=11902336334r=1w=2 ant -version Apache Ant version 1.7.0 compiled on December 13 2006 Trivial modification to the build.xml to include junit with solr. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-363) Use ivy for dependency resolving
[ https://issues.apache.org/jira/browse/SOLR-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Scherler updated SOLR-363: --- Attachment: ivy.support.diff ivy.tar Use ivy for dependency resolving Key: SOLR-363 URL: https://issues.apache.org/jira/browse/SOLR-363 Project: Solr Issue Type: Improvement Reporter: Thorsten Scherler Attachments: ivy.support.diff, ivy.tar First cut on ivy support. Removed all libs in lib/ but not yet for the web app. Patch includes basic ivy rep (tar) for all jars that are ATM not in ivy nor in maven. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-238) [Patch] The tutorial on our website is against trunk which causes confusion by user
[
https://issues.apache.org/jira/browse/SOLR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498364
]
Thorsten Scherler commented on SOLR-238:
cheers Hoss!
1) yes, you can change the name. I will add a new version.
2)
a) no, you can change it in the forrest.properties:
#project.schema-dir=${project.resources-dir}/schema
is the default.
You can change it to something like
project.schema-dir=src/schema
if you want, just uncomment the property.
b) not sure about the path better use the forrest.properties.
3) As I understand it (used it the first time in this contribution) it links to
the *. ent file, giving the benefit that you can import it to your favorite xml
editor:
http://forrest.apache.org/docs_0_70/catalog.html
further (as I understand it) forrest is using it to look up the *.ent file.
[Patch] The tutorial on our website is against trunk which causes confusion
by user
---
Key: SOLR-238
URL: https://issues.apache.org/jira/browse/SOLR-238
Project: Solr
Issue Type: Improvement
Components: documentation
Reporter: Thorsten Scherler
Assigned To: Hoss Man
Attachments: SOLR-238.diff, SOLR-238.diff, SOLR-238.diff, SOLR-238.png
The patch will add a note to the tutorial page with the following headsup:
This is documentation for the development version (TRUNK). Some instructions
may only work if you are working against svn head.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-238) [Patch] The tutorial on our website is against trunk which causes confusion by user
[ https://issues.apache.org/jira/browse/SOLR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Scherler updated SOLR-238: --- Attachment: SOLR-238.diff Patch of the forrest skinconf.xml [Patch] The tutorial on our website is against trunk which causes confusion by user --- Key: SOLR-238 URL: https://issues.apache.org/jira/browse/SOLR-238 Project: Solr Issue Type: Improvement Components: documentation Reporter: Thorsten Scherler Attachments: SOLR-238.diff The patch will add a note to the tutorial page with the following headsup: This is documentation for the development version (TRUNK). Some instructions may only work if you are working against svn head. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-238) [Patch] The tutorial on our website is against trunk which causes confusion by user
[ https://issues.apache.org/jira/browse/SOLR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Scherler updated SOLR-238: --- Attachment: SOLR-238.png screenshot Find window title changed and two new note boxes. [Patch] The tutorial on our website is against trunk which causes confusion by user --- Key: SOLR-238 URL: https://issues.apache.org/jira/browse/SOLR-238 Project: Solr Issue Type: Improvement Components: documentation Reporter: Thorsten Scherler Attachments: SOLR-238.diff, SOLR-238.png The patch will add a note to the tutorial page with the following headsup: This is documentation for the development version (TRUNK). Some instructions may only work if you are working against svn head. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-133) change XmlUpdateRequestHandler to use StAX instead of XPP
[ https://issues.apache.org/jira/browse/SOLR-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494005 ] Thorsten Scherler commented on SOLR-133: What is missing with this issue, where can I give a helping had. change XmlUpdateRequestHandler to use StAX instead of XPP - Key: SOLR-133 URL: https://issues.apache.org/jira/browse/SOLR-133 Project: Solr Issue Type: Improvement Reporter: Hoss Man Attachments: SOLR-133-XmlUpdateRequestHandler-StAX-139.patch, SOLR-133-XmlUpdateRequestHandler-StAX-139.patch, SOLR-133-XmlUpdateRequestHandler-StAX-139.patch, SOLR-133-XmlUpdateRequestHandler-StAX-139.patch, SOLR-133-XmlUpdateRequestHandler-StAX-139.patch, SOLR-133.diff, SOLR-133.diff there has been discussion of using StAX for XML parsing of updates instead of XPP ... opening an issue to track it as a possible improvement (orriginally mentioned in SOLR-61, but that task was more specificly about refactoring the existing code) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-109) variable substitution in lucene query params
[
https://issues.apache.org/jira/browse/SOLR-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thorsten Scherler updated SOLR-109:
---
Attachment: SOLR-109.diff
Hi Hoss, I finally got back to my solr project and to this issue. :)
Hopefully I can contribute more from now on, since the project got funding for
a couple of months.
Please find a complete rewrite of the prior incomplete patch. I tried to stay
as close as your instructions as I understood them. The only part that I did
not understood is the handlers part.
I did a grep for SolrQueryParser but could not find an example where I can call
SolrQueryParser.setParams(SolrParams params) to prepare the substitution
(setSubstitutionSolrParam(String queryText){}).
Can somebody push me into the right direction to finish the patch with a nice
test?
TIA
variable substitution in lucene query params
Key: SOLR-109
URL: https://issues.apache.org/jira/browse/SOLR-109
Project: Solr
Issue Type: New Feature
Reporter: Thorsten Scherler
Attachments: SOLR-109.diff, SOLR-109.diff
Allowing variable substitution in the lucene query params seems pretty slick
... a more general solution might be to modify the SolrQueryParser
directly to have a new void setParamVariables(SolrParams p) method.
http://marc.theaimsgroup.com/?t=11671237641r=1w=2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-85) [PATCH] Add update form to the admin screen
[ https://issues.apache.org/jira/browse/SOLR-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494028 ] Thorsten Scherler commented on SOLR-85: --- Hi Ryan, I just did a quick check of the current trunk and could not found the patch includes (as I understood it from your last comment). How can I help to get the patch into the trunk? [PATCH] Add update form to the admin screen --- Key: SOLR-85 URL: https://issues.apache.org/jira/browse/SOLR-85 Project: Solr Issue Type: New Feature Components: update Reporter: Thorsten Scherler Attachments: solar-85.png, solar-85.png, solar-85.with.file.upload.diff, solar-85.with.file.upload.diff, solar-85.with.file.upload.diff, solar-85.with.file.upload.diff, SOLR-85-UpdatForms-RequestHandlers.patch, SOLR-85-UpdatForms-RequestHandlers.patch, solr-85-with-104.patch, solr-85-with-104.patch, solr-85-with-104.patch, solr-85.diff, solr-85.diff, solr-85.FINAL.diff It would be nice to have a webform to update solr via a http interface instead of using the post.sh. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-133) change XmlUpdateRequestHandler to use StAX instead of XPP
[ https://issues.apache.org/jira/browse/SOLR-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Scherler updated SOLR-133: --- Attachment: SOLR-133.diff Refactoring the XmlUpdateRequestHandler to use constant variables that can be reused by the Stax implementation. Adding a stax implementation for the XmlUpdateRequestHandler. Till now I get an error about missing content stream. NOTE: To make the version compile you need to download the JSR 173 API from http://www.ibiblio.org/maven2/stax/stax-api/1.0/stax-api-1.0.jar and copy it to $SOLR_HOME/lib/. change XmlUpdateRequestHandler to use StAX instead of XPP - Key: SOLR-133 URL: https://issues.apache.org/jira/browse/SOLR-133 Project: Solr Issue Type: Improvement Reporter: Hoss Man Attachments: SOLR-133.diff there has been discussion of using StAX for XML parsing of updates instead of XPP ... opening an issue to track it as a possible improvement (orriginally mentioned in SOLR-61, but that task was more specificly about refactoring the existing code) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-133) change XmlUpdateRequestHandler to use StAX instead of XPP
[ https://issues.apache.org/jira/browse/SOLR-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Scherler updated SOLR-133: --- Attachment: SOLR-133.diff Fixing bugs from first version. Adding workaround for problem with direct use of the handler (never gets a stream). http://www.mail-archive.com/solr-dev@lucene.apache.org/msg02759.html by patching the SolrUpdateServlet Please test, it works fine for me. change XmlUpdateRequestHandler to use StAX instead of XPP - Key: SOLR-133 URL: https://issues.apache.org/jira/browse/SOLR-133 Project: Solr Issue Type: Improvement Reporter: Hoss Man Attachments: SOLR-133.diff, SOLR-133.diff there has been discussion of using StAX for XML parsing of updates instead of XPP ... opening an issue to track it as a possible improvement (orriginally mentioned in SOLR-61, but that task was more specificly about refactoring the existing code) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-133) change XmlUpdateRequestHandler to use StAX instead of XPP
[ https://issues.apache.org/jira/browse/SOLR-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470001 ] Thorsten Scherler commented on SOLR-133: @Larrea 1) standards-based 2) agree 3) agree 4) agree StAX is become a standard. Not as fast as SAX but nearly. IMO the StAX implementation is as easy to follow as the xpp, personally I think even easier. change XmlUpdateRequestHandler to use StAX instead of XPP - Key: SOLR-133 URL: https://issues.apache.org/jira/browse/SOLR-133 Project: Solr Issue Type: Improvement Reporter: Hoss Man Attachments: SOLR-133.diff, SOLR-133.diff there has been discussion of using StAX for XML parsing of updates instead of XPP ... opening an issue to track it as a possible improvement (orriginally mentioned in SOLR-61, but that task was more specificly about refactoring the existing code) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-61) move XML update parsing out of SolrCore
[ https://issues.apache.org/jira/browse/SOLR-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469450 ] Thorsten Scherler commented on SOLR-61: --- Hi Hoss, I personally would not close this issue, since we have completed one point but not the second one. We have decoupled the XML parsing from SolrCore, but not moved to StAX based parsing. move XML update parsing out of SolrCore --- Key: SOLR-61 URL: https://issues.apache.org/jira/browse/SOLR-61 Project: Solr Issue Type: Improvement Reporter: Yonik Seeley Priority: Minor The XML parsing in SolrCore should be decoupled and moved out. We also might consider moving to StAX based parsing, as it is now a standard and will be included in Java6 (Woodstox could be used for Java5). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-85) [PATCH] Add update form to the admin screen
[ https://issues.apache.org/jira/browse/SOLR-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469074 ] Thorsten Scherler commented on SOLR-85: --- Hi Ryan, sorry for coming back so late on this, but I need to finish up the first version of a customer project. Anyway, I saw that SOLR-104 is now applied meaning your last patch on this issue should work fine, right. Are they any other blocker on this issue? salu2 [PATCH] Add update form to the admin screen --- Key: SOLR-85 URL: https://issues.apache.org/jira/browse/SOLR-85 Project: Solr Issue Type: New Feature Components: update Reporter: Thorsten Scherler Attachments: solar-85.png, solar-85.png, solar-85.with.file.upload.diff, solar-85.with.file.upload.diff, solar-85.with.file.upload.diff, solar-85.with.file.upload.diff, solr-85-with-104.patch, solr-85.diff, solr-85.diff, solr-85.FINAL.diff It would be nice to have a webform to update solr via a http interface instead of using the post.sh. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-61) move XML update parsing out of SolrCore
[ https://issues.apache.org/jira/browse/SOLR-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469076 ] Thorsten Scherler commented on SOLR-61: --- Hi all, I am keen to give this issue a go, somebody can give some hints where to start. TIA salu2 move XML update parsing out of SolrCore --- Key: SOLR-61 URL: https://issues.apache.org/jira/browse/SOLR-61 Project: Solr Issue Type: Improvement Reporter: Yonik Seeley Priority: Minor The XML parsing in SolrCore should be decoupled and moved out. We also might consider moving to StAX based parsing, as it is now a standard and will be included in Java6 (Woodstox could be used for Java5). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SOLR-130) [Patch] [Docu] Starting a mySolr document, which tries to explain how to setup a custom solr instance
[Patch] [Docu] Starting a mySolr document, which tries to explain how to setup a custom solr instance - Key: SOLR-130 URL: https://issues.apache.org/jira/browse/SOLR-130 Project: Solr Issue Type: Task Reporter: Thorsten Scherler While developing a custom search server based on solr I took some notes about the do's and don'ts. The initial patch is not a fully finished document but may invite other devs to enhance it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-109) variable substitution in lucene query params
[
https://issues.apache.org/jira/browse/SOLR-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thorsten Scherler updated SOLR-109:
---
Attachment: SOLR-109.diff
This is a first start.
What still is missing is ... a more general solution might be to modify the
SolrQueryParser
directly to have a new void setParamVariables(SolrParams p) method. if
it's called (with non null input), then any string that SolrQueryParser
instance is asked to parse would first be preprocessed looking for the ${}
pattern and pulling the values out of the SOlrParams instance.
I need to have a closer look on what Hoss means exactly with this. However I
get lots of error after an svn up and I am not sure whether my local changes
has caused this.
variable substitution in lucene query params
Key: SOLR-109
URL: https://issues.apache.org/jira/browse/SOLR-109
Project: Solr
Issue Type: New Feature
Reporter: Thorsten Scherler
Attachments: SOLR-109.diff
Allowing variable substitution in the lucene query params seems pretty slick
... a more general solution might be to modify the SolrQueryParser
directly to have a new void setParamVariables(SolrParams p) method.
http://marc.theaimsgroup.com/?t=11671237641r=1w=2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-86) [PATCH] standalone updater cli based on httpClient
[
https://issues.apache.org/jira/browse/SOLR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465327
]
Thorsten Scherler commented on SOLR-86:
---
Yeah, I know what you mean (had a similar problem today).
if (!file.isDirectory()){
tool.postFile(file, out);
}
should fix that.
TIA
[PATCH] standalone updater cli based on httpClient
---
Key: SOLR-86
URL: https://issues.apache.org/jira/browse/SOLR-86
Project: Solr
Issue Type: New Feature
Components: update
Reporter: Thorsten Scherler
Attachments: simple-post-using-urlconnection-approach.patch,
solr-86.diff, solr-86.diff
We need a cross platform replacement for the post.sh.
The attached code is a direct replacement of the post.sh since it is actually
doing the same exact thing.
In the future one can extend the CLI with other feature like auto commit,
etc..
Right now the code assumes that SOLR-85 is applied since we using the servlet
of this issue to actually do the update.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SOLR-86) [PATCH] standalone updater cli based on httpClient
[
https://issues.apache.org/jira/browse/SOLR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464737
]
Thorsten Scherler commented on SOLR-86:
---
Hi Hoiss, I had a look at your version and it is good as gold.
I personally prefer the httpClient since the method is smaller but Bertrand and
ourself are right, the dependency jar price for a simple replacement is ATM too
high.
The only thing that I would add is directory support:
...
+ if (srcFile.exists()) {
+if (srcFile.isDirectory()) {
+File[] fileSet = srcFile.listFiles();
+for (int i = 0; i fileSet.length; i++) {
+File file = fileSet[i];
+tool.postFile(file, out);
+} else {
+tool.postFile(srcFile, out);
+}
+ System.out.println();
+} else {
+ System.err.println(srcFile + does not exist);
+}
I agree to your patch as official replacement of the post.sh. I further agree
with Bertrand that we may include patch as base demonstration for more complex
client apps.
[PATCH] standalone updater cli based on httpClient
---
Key: SOLR-86
URL: https://issues.apache.org/jira/browse/SOLR-86
Project: Solr
Issue Type: New Feature
Components: update
Reporter: Thorsten Scherler
Attachments: simple-post-using-urlconnection-approach.patch,
solr-86.diff, solr-86.diff
We need a cross platform replacement for the post.sh.
The attached code is a direct replacement of the post.sh since it is actually
doing the same exact thing.
In the future one can extend the CLI with other feature like auto commit,
etc..
Right now the code assumes that SOLR-85 is applied since we using the servlet
of this issue to actually do the update.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SOLR-109) variable substitution in lucene query params
variable substitution in lucene query params Key: SOLR-109 URL: https://issues.apache.org/jira/browse/SOLR-109 Project: Solr Issue Type: New Feature Reporter: Thorsten Scherler Allowing variable substitution in the lucene query params seems pretty slick ... a more general solution might be to modify the SolrQueryParser directly to have a new void setParamVariables(SolrParams p) method. http://marc.theaimsgroup.com/?t=11671237641r=1w=2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SOLR-30) Java client code for performing searches against a Solr instance
[
http://issues.apache.org/jira/browse/SOLR-30?page=comments#action_12460863 ]
Thorsten Scherler commented on SOLR-30:
---
Hi all,
I had a look at the code and I do not understand a couple of things.
Since the client can request any response format by defining it in the query
string I am not sure whether the
protected Response createResponse(final String _xml, final ListString
_fields) throws SAXException, IOException, ParserConfigurationException,
JDOMException {
makes so much sense at all.
IMO the java client should make it easy to search a solr server with an e.g.
custom servlet. This way we could leverage all helper classes to connect to the
server into the client. What format will be returned depends on the type
defined in the query string that is the reason why I do not thing the JDOM
stuff makes sense.
Further the different public Response search methods lead is IMO not generic
enough, why not simply use
public Response search(String _query, ListNameValuePair params) {
...
}
and returning directly the solr response. Then the calling method would need to
deal with the raw response.
Java client code for performing searches against a Solr instance
Key: SOLR-30
URL: http://issues.apache.org/jira/browse/SOLR-30
Project: Solr
Issue Type: New Feature
Components: search
Reporter: Philip Jacob
Priority: Minor
Attachments: solrsearcher-client.zip
Here are a few classes that connect to a Solr instance to perform searches.
Results are returned in a Response object. The Response encapsulates a
ListMapString,Field that gives you access to the key data in the results.
This is the main part that I'm looking for comments on.
There are 2 dependencies for this code: JDOM and Commons HttpClient. I'll
remove the JDOM dependency in favor of regular DOM at some point, but I think
that the HttpClient dependency is worthwhile here. There's a lot that can be
exploited with HttpClient that isn't demonstrated in this class. The purpose
here is mainly to get feedback on the API of SolrSearcher before I start
optimizing anything.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SOLR-90) Typo in java docs of QueryParsing.java
Typo in java docs of QueryParsing.java --- Key: SOLR-90 URL: http://issues.apache.org/jira/browse/SOLR-90 Project: Solr Issue Type: Improvement Reporter: Thorsten Scherler Index: /home/thorsten/src/apache/solr/src/java/org/apache/solr/search/QueryParsing.java === --- /home/thorsten/src/apache/solr/src/java/org/apache/solr/search/QueryParsing.java (revision 489078) +++ /home/thorsten/src/apache/solr/src/java/org/apache/solr/search/QueryParsing.java (working copy) @@ -408,7 +408,7 @@ * The benefit of using this method instead of calling * codeQuery.toString/code directly is that it knows about the data * types of each field, so any field which is encoded in a particularly - * complex way is still readable. The downside is thta it only knows + * complex way is still readable. The downside is that it only knows * about built in Query types, and will not be able to format custom * Query classes. * /p -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SOLR-88) Solr index cannot be opened with luke anymore
Solr index cannot be opened with luke anymore - Key: SOLR-88 URL: http://issues.apache.org/jira/browse/SOLR-88 Project: Solr Issue Type: Bug Reporter: Thorsten Scherler http://marc.theaimsgroup.com/?l=solr-devm=116661341524556w=2 ...I notice a very weird problem that I do not understand. I tried to open the solr index with luke on trunk and it fails with: java.io.FileNotFoundException: $PATH/solr/data/index/_0.f1 (No such file or directory)... I am using lukeall.jar version 0.6. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SOLR-88) Solr index cannot be opened with luke anymore
[ http://issues.apache.org/jira/browse/SOLR-88?page=comments#action_12459920 ] Thorsten Scherler commented on SOLR-88: --- I think found the revision: svn up -r487364 . Before this revision I can open the index with luke. After this commit I cannot do it anymore. Seeing the changes it seems that @omitNorms=true is svn diff -r487340:487364 Index: example/solr/conf/schema.xml === --- example/solr/conf/schema.xml(revision 487340) +++ example/solr/conf/schema.xml(revision 487364) @@ -47,10 +47,10 @@ limits compression (if enabled in the derived fields) to values which exceed a certain size (in characters). -- -fieldtype name=string class=solr.StrField sortMissingLast=true/ +fieldtype name=string class=solr.StrField sortMissingLast=true omitNorms=true/ !-- boolean type: true or false -- -fieldtype name=boolean class=solr.BoolField sortMissingLast=true/ +fieldtype name=boolean class=solr.BoolField sortMissingLast=true omitNorms=true/ !-- The optional sortMissingLast and sortMissingFirst attributes are currently supported on types that are sorted internally as strings. @@ -69,20 +69,20 @@ !-- numeric field types that store and index the text value verbatim (and hence don't support range queries, since the lexicographic ordering isn't equal to the numeric ordering) -- -fieldtype name=integer class=solr.IntField/ -fieldtype name=long class=solr.LongField/ -fieldtype name=float class=solr.FloatField/ -fieldtype name=double class=solr.DoubleField/ +fieldtype name=integer class=solr.IntField omitNorms=true/ +fieldtype name=long class=solr.LongField omitNorms=true/ +fieldtype name=float class=solr.FloatField omitNorms=true/ +fieldtype name=double class=solr.DoubleField omitNorms=true/ !-- Numeric field types that manipulate the value into a string value that isn't human-readable in its internal form, but with a lexicographic ordering the same as the numeric ordering, so that range queries work correctly. -- -fieldtype name=sint class=solr.SortableIntField sortMissingLast=true/ -fieldtype name=slong class=solr.SortableLongField sortMissingLast=true/ -fieldtype name=sfloat class=solr.SortableFloatField sortMissingLast=true/ -fieldtype name=sdouble class=solr.SortableDoubleField sortMissingLast=true/ +fieldtype name=sint class=solr.SortableIntField sortMissingLast=true omitNorms=true/ +fieldtype name=slong class=solr.SortableLongField sortMissingLast=true omitNorms=true/ +fieldtype name=sfloat class=solr.SortableFloatField sortMissingLast=true omitNorms=true/ +fieldtype name=sdouble class=solr.SortableDoubleField sortMissingLast=true omitNorms=true/ !-- The format for this date field is of the form 1995-12-31T23:59:59Z, and @@ -105,7 +105,7 @@ Consult the DateField javadocs for more information. -- -fieldtype name=date class=solr.DateField sortMissingLast=true/ +fieldtype name=date class=solr.DateField sortMissingLast=true omitNorms=true/ !-- solr.TextField allows the specification of custom text analyzers specified as a tokenizer and a list of token filters. Different @@ -183,24 +183,25 @@ fields !-- Valid attributes for fields: - name: mandatory - the name for the field - type: mandatory - the name of a previously defined type from the types section - indexed: true if this field should be indexed (searchable) - stored: true if this field should be retrievable - compressed: [false] if this field should be stored using gzip compression - (this will only apply if the field type is compressable; among -the standard field types, only TextField and StrField are) - multiValued: true if this field may contain multiple values per document - omitNorms: (expert) set to true to omit the norms associated with this field - (this disables length normalization and index-time boosting for the field) - + name: mandatory - the name for the field + type: mandatory - the name of a previously defined type from the types section + indexed: true if this field should be indexed (searchable or sortable) + stored: true if this field should be retrievable + compressed: [false] if this field should be stored using gzip compression + (this will only apply if the field type is compressable; among + the standard field types, only TextField and StrField are) + multiValued: true if this field may contain multiple values per document + omitNorms: (expert) set to true to omit the norms associated with + this field (this disables length normalization and index-time + boosting for the field, and saves some memory).
[jira] Commented: (SOLR-88) Solr index cannot be opened with luke anymore
[ http://issues.apache.org/jira/browse/SOLR-88?page=comments#action_12459926 ] Thorsten Scherler commented on SOLR-88: --- Removing omitNorms=true from the schema.xml fixes this issue. Solr index cannot be opened with luke anymore - Key: SOLR-88 URL: http://issues.apache.org/jira/browse/SOLR-88 Project: Solr Issue Type: Bug Reporter: Thorsten Scherler Attachments: commits.since.11-27.log http://marc.theaimsgroup.com/?l=solr-devm=116661341524556w=2 ...I notice a very weird problem that I do not understand. I tried to open the solr index with luke on trunk and it fails with: java.io.FileNotFoundException: $PATH/solr/data/index/_0.f1 (No such file or directory)... I am using lukeall.jar version 0.6. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SOLR-88) Solr index cannot be opened with luke anymore
[ http://issues.apache.org/jira/browse/SOLR-88?page=comments#action_12459937 ] Thorsten Scherler commented on SOLR-88: --- Cheers Erik. That is good to know. Solr index cannot be opened with luke anymore - Key: SOLR-88 URL: http://issues.apache.org/jira/browse/SOLR-88 Project: Solr Issue Type: Bug Reporter: Thorsten Scherler Attachments: commits.since.11-27.log http://marc.theaimsgroup.com/?l=solr-devm=116661341524556w=2 ...I notice a very weird problem that I do not understand. I tried to open the solr index with luke on trunk and it fails with: java.io.FileNotFoundException: $PATH/solr/data/index/_0.f1 (No such file or directory)... I am using lukeall.jar version 0.6. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SOLR-86) [PATCH] standalone updater cli based on httpClient
[PATCH] standalone updater cli based on httpClient --- Key: SOLR-86 URL: http://issues.apache.org/jira/browse/SOLR-86 Project: Solr Issue Type: New Feature Components: update Reporter: Thorsten Scherler We need a cross platform replacement for the post.sh. The attached code is a direct replacement of the post.sh since it is actually doing the same exact thing. In the future one can extend the CLI with other feature like auto commit, etc.. Right now the code assumes that SOLR-85 is applied since we using the servlet of this issue to actually do the update. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SOLR-86) [PATCH] standalone updater cli based on httpClient
[ http://issues.apache.org/jira/browse/SOLR-86?page=comments#action_12459385 ] Thorsten Scherler commented on SOLR-86: --- Index: src/tools/updater/lib/commons-httpclient-3.0.1.jar Index: src/tools/updater/lib/commons-codec-1.3.jar Index: src/tools/updater/lib/commons-logging-1.1.jar see http://jakarta.apache.org/commons/httpclient/dependencies.html for the download pages. After applying the patch and adding above libs to src/tools/updater/lib you can install the updater with: ant updater.jar and follow the instructions given in this target. [PATCH] standalone updater cli based on httpClient --- Key: SOLR-86 URL: http://issues.apache.org/jira/browse/SOLR-86 Project: Solr Issue Type: New Feature Components: update Reporter: Thorsten Scherler Attachments: solr-86.diff We need a cross platform replacement for the post.sh. The attached code is a direct replacement of the post.sh since it is actually doing the same exact thing. In the future one can extend the CLI with other feature like auto commit, etc.. Right now the code assumes that SOLR-85 is applied since we using the servlet of this issue to actually do the update. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SOLR-85) [PATCH] Add update form to the admin screen
[ http://issues.apache.org/jira/browse/SOLR-85?page=all ] Thorsten Scherler updated SOLR-85: -- Attachment: solar-85.with.file.upload.diff The solar-85.with.file.upload.diff is further extending the current patch and makes the old diffs obsolete. I sadly have no power to remove the obsolete attachments. Sorry. This patch is providing a way to upload a update document. On Fri, 2006-12-15 at 04:57 +0100, Zaheed Haque wrote: ... Maybe you can add a file upload button. what I mean is that lets say you have a file data.xml or data.txt or data.tar.gzip (maybe gzip or tar format can be done later) with many solr records..like .. doc /doc etc.. more.. doc /doc Then you could uplaod that file and presto you updated the index.. that would be cool. I still would like to have the current textarea box its cool to be able to delete a doc/doc directly ot update a doc directly.. The current implementation is assuming the uploaded file is an xml document. [PATCH] Add update form to the admin screen --- Key: SOLR-85 URL: http://issues.apache.org/jira/browse/SOLR-85 Project: Solr Issue Type: New Feature Components: update Reporter: Thorsten Scherler Attachments: solar-85.png, solar-85.with.file.upload.diff, solr-85.diff, solr-85.diff, solr-85.FINAL.diff It would be nice to have a webform to update solr via a http interface instead of using the post.sh. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SOLR-85) [PATCH] Add update form to the admin screen
[ http://issues.apache.org/jira/browse/SOLR-85?page=comments#action_12458779 ] Thorsten Scherler commented on SOLR-85: --- @Hoss yeah I understand your concerns and actually the update form is a wee bit apart from the rest of the forms in admin area. It is more a general approach rather then focused on the examples. Maybe this whole patch good be better packaged as plugin but I am still new to solr and I am not sure how I good patch the web.xml with a plugin. Any pointers appreciated. The next thing on my list is to write a small cli based on httpclient to send the update docs as alternative of the post.sh. BTW the patch needs lib/commons-fileupload-1.1.1.jar - http://jakarta.apache.org/site/downloads/downloads_commons-fileupload.cgi lib/commons-io-1.2.jar - http://jakarta.apache.org/site/downloads/downloads_commons-io.cgi [PATCH] Add update form to the admin screen --- Key: SOLR-85 URL: http://issues.apache.org/jira/browse/SOLR-85 Project: Solr Issue Type: New Feature Components: update Reporter: Thorsten Scherler Attachments: solar-85.png, solar-85.with.file.upload.diff, solr-85.diff, solr-85.diff, solr-85.FINAL.diff It would be nice to have a webform to update solr via a http interface instead of using the post.sh. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SOLR-85) [PATCH] Add update form to the admin screen
[ http://issues.apache.org/jira/browse/SOLR-85?page=all ] Thorsten Scherler updated SOLR-85: -- Attachment: solar-85.png New screenshot including the new features. [PATCH] Add update form to the admin screen --- Key: SOLR-85 URL: http://issues.apache.org/jira/browse/SOLR-85 Project: Solr Issue Type: New Feature Components: update Reporter: Thorsten Scherler Attachments: solar-85.png, solar-85.png, solar-85.with.file.upload.diff, solr-85.diff, solr-85.diff, solr-85.FINAL.diff It would be nice to have a webform to update solr via a http interface instead of using the post.sh. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SOLR-83) DOCU: Quickstart note about how to make the example working in src version
DOCU: Quickstart note about how to make the example working in src version --- Key: SOLR-83 URL: http://issues.apache.org/jira/browse/SOLR-83 Project: Solr Issue Type: Improvement Reporter: Thorsten Scherler Priority: Minor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SOLR-83) DOCU: Quickstart note about how to make the example working in src version
[ http://issues.apache.org/jira/browse/SOLR-83?page=all ] Thorsten Scherler updated SOLR-83: -- Attachment: SOLR-83.diff patch for $SOLR_HOME/README.txt DOCU: Quickstart note about how to make the example working in src version -- Key: SOLR-83 URL: http://issues.apache.org/jira/browse/SOLR-83 Project: Solr Issue Type: Improvement Reporter: Thorsten Scherler Priority: Minor Attachments: SOLR-83.diff -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SOLR-85) [PATCH] Add update form to the admin screen
[PATCH] Add update form to the admin screen --- Key: SOLR-85 URL: http://issues.apache.org/jira/browse/SOLR-85 Project: Solr Issue Type: New Feature Components: update Reporter: Thorsten Scherler It would be nice to have a webform to update solr via a http interface instead of using the post.sh. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SOLR-85) [PATCH] Add update form to the admin screen
[ http://issues.apache.org/jira/browse/SOLR-85?page=all ] Thorsten Scherler updated SOLR-85: -- Attachment: solar-85.png Screenshot of the extended admin screen [PATCH] Add update form to the admin screen --- Key: SOLR-85 URL: http://issues.apache.org/jira/browse/SOLR-85 Project: Solr Issue Type: New Feature Components: update Reporter: Thorsten Scherler Attachments: solar-85.png It would be nice to have a webform to update solr via a http interface instead of using the post.sh. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SOLR-85) [PATCH] Add update form to the admin screen
[ http://issues.apache.org/jira/browse/SOLR-85?page=comments#action_12458470 ] Thorsten Scherler commented on SOLR-85: --- This new feature allows you to update your solr instance via web. For your convenience I add the a commit button to commit directly afterwards. Just add your update statement into the form and submit. Try with add doc field name=idSP2514N/field field name=nameSamsung SpinPoint P120 SP2514N - hard drive - 250 GB - ATA-133/field field name=manuSamsung Electronics Co. Ltd./field field name=catelectronics/field field name=cathard drive/field field name=features7200RPM, 8MB cache, IDE Ultra ATA-133/field field name=featuresNoiseGuard, SilentSeek technology, Fluid Dynamic Bearing (FDB) motor/field field name=price92/field field name=popularity6/field field name=inStocktrue/field /doc /add [PATCH] Add update form to the admin screen --- Key: SOLR-85 URL: http://issues.apache.org/jira/browse/SOLR-85 Project: Solr Issue Type: New Feature Components: update Reporter: Thorsten Scherler Attachments: solar-85.png, solr-85.diff, solr-85.diff, solr-85.FINAL.diff It would be nice to have a webform to update solr via a http interface instead of using the post.sh. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
