remote streaming
I'm writing up a wiki page for the update plugin changes. I just realized that remote streaming is enabled in the default solrconfig.xml Can we change that to false? My patch had it set to "true" and i forgot to change it back. thanks ryan
[jira] Updated: (SOLR-126) Auto-commit documents after time interval
[ https://issues.apache.org/jira/browse/SOLR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley updated SOLR-126: --- Attachment: AutoCommit.patch > Auto-commit documents after time interval > - > > Key: SOLR-126 > URL: https://issues.apache.org/jira/browse/SOLR-126 > Project: Solr > Issue Type: Improvement > Components: update >Reporter: Ryan McKinley >Priority: Minor > Attachments: AutoCommit.patch, AutocommitingUpdateRequestHandler.patch > > > If an index is getting updated from multiple sources and needs to add > documents reasonably quickly, there should be a good solr side mechanism to > help prevent the client from spawning multiple overlapping commands. > My specific use case is sending each document to solr every time hibernate > saves an object (see SOLR-20). This happens from multiple machines > simultaneously. I'd like solr to make sure the documents are committed > within a second. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-126) Auto-commit documents after time interval
[ https://issues.apache.org/jira/browse/SOLR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468561 ] Ryan McKinley commented on SOLR-126: I just posted AutoCommit.patch This patch modifies DirectUpdateHandler2.CommentTracker to automatically commit a after a certain period. As written, It should never start multiple commits at the same time. I think this is ready to go. > Auto-commit documents after time interval > - > > Key: SOLR-126 > URL: https://issues.apache.org/jira/browse/SOLR-126 > Project: Solr > Issue Type: Improvement > Components: update >Reporter: Ryan McKinley >Priority: Minor > Attachments: AutoCommit.patch, AutocommitingUpdateRequestHandler.patch > > > If an index is getting updated from multiple sources and needs to add > documents reasonably quickly, there should be a good solr side mechanism to > help prevent the client from spawning multiple overlapping commands. > My specific use case is sending each document to solr every time hibernate > saves an object (see SOLR-20). This happens from multiple machines > simultaneously. I'd like solr to make sure the documents are committed > within a second. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-84) New Solr logo?
[ https://issues.apache.org/jira/browse/SOLR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley updated SOLR-84: -- Attachment: logo-solr-e.jpg > New Solr logo? > -- > > Key: SOLR-84 > URL: https://issues.apache.org/jira/browse/SOLR-84 > Project: Solr > Issue Type: Improvement >Reporter: Bertrand Delacretaz >Priority: Minor > Attachments: logo-solr-e.jpg, logo-solr-source-files-take2.zip, > solr-84-source-files.zip, solr-logo-20061214.jpg, solr-logo-20061218.JPG, > solr-logo-20070124.JPG, solr.jpg, solr.jpg > > > Following up on SOLR-76, our trainee Nicolas Barbay (nicolas (put at here) > sarraux-dessous.ch) has reworked his logo proposal to be more "solar". > This can either be the start of a logo contest, or if people like it we could > adopt it. The gradients can make it a bit hard to integrate, not sure if this > is really a problem. > WDYT? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-84) New Solr logo?
[ https://issues.apache.org/jira/browse/SOLR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley updated SOLR-84: -- Attachment: logo-solr-d.jpg > New Solr logo? > -- > > Key: SOLR-84 > URL: https://issues.apache.org/jira/browse/SOLR-84 > Project: Solr > Issue Type: Improvement >Reporter: Bertrand Delacretaz >Priority: Minor > Attachments: logo-solr-d.jpg, logo-solr-e.jpg, > logo-solr-source-files-take2.zip, solr-84-source-files.zip, > solr-logo-20061214.jpg, solr-logo-20061218.JPG, solr-logo-20070124.JPG, > solr.jpg, solr.jpg > > > Following up on SOLR-76, our trainee Nicolas Barbay (nicolas (put at here) > sarraux-dessous.ch) has reworked his logo proposal to be more "solar". > This can either be the start of a logo contest, or if people like it we could > adopt it. The gradients can make it a bit hard to integrate, not sure if this > is really a problem. > WDYT? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-84) New Solr logo?
[ https://issues.apache.org/jira/browse/SOLR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468564 ] Ryan McKinley commented on SOLR-84: --- More variations from Juan. So far I like logo-solr-e.jpg best, perhaps with a larger sun and shorter "r" Make sure to look at the original image - not the one JIRA resizes. > New Solr logo? > -- > > Key: SOLR-84 > URL: https://issues.apache.org/jira/browse/SOLR-84 > Project: Solr > Issue Type: Improvement >Reporter: Bertrand Delacretaz >Priority: Minor > Attachments: logo-solr-d.jpg, logo-solr-e.jpg, > logo-solr-source-files-take2.zip, solr-84-source-files.zip, > solr-logo-20061214.jpg, solr-logo-20061218.JPG, solr-logo-20070124.JPG, > solr.jpg, solr.jpg > > > Following up on SOLR-76, our trainee Nicolas Barbay (nicolas (put at here) > sarraux-dessous.ch) has reworked his logo proposal to be more "solar". > This can either be the start of a logo contest, or if people like it we could > adopt it. The gradients can make it a bit hard to integrate, not sure if this > is really a problem. > WDYT? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (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:all-tabpanel ] Ryan McKinley updated SOLR-85: -- Attachment: solr-85-with-104.patch > [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-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_12468580 ] Ryan McKinley commented on SOLR-85: --- just posted solr-85-with-104.patch This uses SOLR-104 to pass the content with stream.body. This patch includes some small modification to SOLR-104, including: * it call rsp.setException(e) * it lets you add the 'commit' or 'optimize' command to XmlUpdate * XmlUpdate uses req.getCore() rather then SolrCore.getSolrCore() where possible > [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] Created: (SOLR-128) Include Newer version of Jetty
Include Newer version of Jetty -- Key: SOLR-128 URL: https://issues.apache.org/jira/browse/SOLR-128 Project: Solr Issue Type: Improvement Components: update Reporter: Ryan McKinley Priority: Minor It would be good to include an up-to-date jetty version for the example. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-128) Include Newer version of Jetty
[ https://issues.apache.org/jira/browse/SOLR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468588 ] Ryan McKinley commented on SOLR-128: I tried running the example with jetty 6.1. In less then 5 mins, I had everything working smoothly. The only issue I see is the JSP jar files are huge (~4MB) The current example folder includes settings and jars for JMX, is that necessary? > Include Newer version of Jetty > -- > > Key: SOLR-128 > URL: https://issues.apache.org/jira/browse/SOLR-128 > Project: Solr > Issue Type: Improvement > Components: update >Reporter: Ryan McKinley >Priority: Minor > > It would be good to include an up-to-date jetty version for the example. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-128) Include Newer version of Jetty
[ https://issues.apache.org/jira/browse/SOLR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley updated SOLR-128: --- Attachment: start.jar > Include Newer version of Jetty > -- > > Key: SOLR-128 > URL: https://issues.apache.org/jira/browse/SOLR-128 > Project: Solr > Issue Type: Improvement > Components: update >Reporter: Ryan McKinley >Priority: Minor > Attachments: Jetty6.config.patch, start.jar > > > It would be good to include an up-to-date jetty version for the example. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-128) Include Newer version of Jetty
[ https://issues.apache.org/jira/browse/SOLR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley updated SOLR-128: --- Attachment: Jetty6.config.patch > Include Newer version of Jetty > -- > > Key: SOLR-128 > URL: https://issues.apache.org/jira/browse/SOLR-128 > Project: Solr > Issue Type: Improvement > Components: update >Reporter: Ryan McKinley >Priority: Minor > Attachments: Jetty6.config.patch, start.jar > > > It would be good to include an up-to-date jetty version for the example. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-128) Include Newer version of Jetty
[ https://issues.apache.org/jira/browse/SOLR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley updated SOLR-128: --- Attachment: lib.zip > Include Newer version of Jetty > -- > > Key: SOLR-128 > URL: https://issues.apache.org/jira/browse/SOLR-128 > Project: Solr > Issue Type: Improvement > Components: update >Reporter: Ryan McKinley >Priority: Minor > Attachments: Jetty6.config.patch, lib.zip, start.jar > > > It would be good to include an up-to-date jetty version for the example. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: Performance Tuning
After 8 hours: 552955 documents -> 554827 (average s: about 3000/hour, but many of them are currently updates of existing records) > Memory: 3.5Gb of 11.7Gb RAM, 0 swap. > Index Files: 62 items, 200Mb 197 files, 223 Mb After stopping and issuing explicitly (it took maybe 20 seconds): 17 files, 207.1 Mb > I changed memory limits, restored default solr-config.xml, and I am trying > to execute it again: > 4Gb - database > 1Gb - Tomcat+Solr > 512Mb - Tomcat+Cocoon > 2Gb - Standalone Java Solr-Client > - Apache Httpd (default settings; probably 1Gb total)
[jira] Commented: (SOLR-128) Include Newer version of Jetty
[ https://issues.apache.org/jira/browse/SOLR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468647 ] Yonik Seeley commented on SOLR-128: --- We could probably ditch the JMX stuff as we don't currently use it... or does Jetty export some cool stuff via JMX that we might want to point people at for debugging? If we go with JSP 2.1, we should just remember not to use any 2.1 specific features yet... most containers aren't quite there yet. The latest stable version of Tomcat 5.5.20 is only on Servlet 2.4/JSP 2.0 > Include Newer version of Jetty > -- > > Key: SOLR-128 > URL: https://issues.apache.org/jira/browse/SOLR-128 > Project: Solr > Issue Type: Improvement > Components: update >Reporter: Ryan McKinley >Priority: Minor > Attachments: Jetty6.config.patch, lib.zip, start.jar > > > It would be good to include an up-to-date jetty version for the example. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-84) New Solr logo?
[ https://issues.apache.org/jira/browse/SOLR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468654 ] Bill Au commented on SOLR-84: - My vote is for logo-solr-d.jpg. The r now matches the s in width and the sun is easier on the eye. > New Solr logo? > -- > > Key: SOLR-84 > URL: https://issues.apache.org/jira/browse/SOLR-84 > Project: Solr > Issue Type: Improvement >Reporter: Bertrand Delacretaz >Priority: Minor > Attachments: logo-solr-d.jpg, logo-solr-e.jpg, > logo-solr-source-files-take2.zip, solr-84-source-files.zip, > solr-logo-20061214.jpg, solr-logo-20061218.JPG, solr-logo-20070124.JPG, > solr.jpg, solr.jpg > > > Following up on SOLR-76, our trainee Nicolas Barbay (nicolas (put at here) > sarraux-dessous.ch) has reworked his logo proposal to be more "solar". > This can either be the start of a logo contest, or if people like it we could > adopt it. The gradients can make it a bit hard to integrate, not sure if this > is really a problem. > WDYT? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-128) Include Newer version of Jetty
[ https://issues.apache.org/jira/browse/SOLR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468660 ] Yonik Seeley commented on SOLR-128: --- BTW, there's a Jetty 6.1.1 out... > Include Newer version of Jetty > -- > > Key: SOLR-128 > URL: https://issues.apache.org/jira/browse/SOLR-128 > Project: Solr > Issue Type: Improvement > Components: update >Reporter: Ryan McKinley >Priority: Minor > Attachments: Jetty6.config.patch, lib.zip, start.jar > > > It would be good to include an up-to-date jetty version for the example. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-84) New Solr logo?
[ https://issues.apache.org/jira/browse/SOLR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468663 ] Yonik Seeley commented on SOLR-84: -- in logo-solr-d.jpg, should the "r" be the same height as the "s", or is it intentionally shorter? > New Solr logo? > -- > > Key: SOLR-84 > URL: https://issues.apache.org/jira/browse/SOLR-84 > Project: Solr > Issue Type: Improvement >Reporter: Bertrand Delacretaz >Priority: Minor > Attachments: logo-solr-d.jpg, logo-solr-e.jpg, > logo-solr-source-files-take2.zip, solr-84-source-files.zip, > solr-logo-20061214.jpg, solr-logo-20061218.JPG, solr-logo-20070124.JPG, > solr.jpg, solr.jpg > > > Following up on SOLR-76, our trainee Nicolas Barbay (nicolas (put at here) > sarraux-dessous.ch) has reworked his logo proposal to be more "solar". > This can either be the start of a logo contest, or if people like it we could > adopt it. The gradients can make it a bit hard to integrate, not sure if this > is really a problem. > WDYT? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SOLR-129) Solrb - UTF 8 Support for add/delete
Solrb - UTF 8 Support for add/delete Key: SOLR-129 URL: https://issues.apache.org/jira/browse/SOLR-129 Project: Solr Issue Type: Bug Components: clients - ruby - flare Environment: OSX Reporter: Antonio Eggberg Hi: This could be a ruby utf-8 bug. Anyway when I try to do a UTF-8 document add via post.sh and then do query via Solr Admin everything works as it should. However using the solrb ruby lib or flare UTF-8 doc add doesn't work as it should. I am not sure what I am doing wrong and I don't think its Solr cos it works as it should. Could this be a famous utf-8 ruby bug? I am using ruby 1.8.5 with rails 1.2.1 Cheers -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: remote streaming
On 1/30/07, Ryan McKinley <[EMAIL PROTECTED]> wrote: I'm writing up a wiki page for the update plugin changes. I just realized that remote streaming is enabled in the default solrconfig.xml Can we change that to false? +1, I'll do it. -Yonik
Re: [Solr Wiki] Update of "SolrRequestHandler" by ryan
: New page: : = SolrRequestHandler = thanks for writing this up ryan ... I was starting to wonder how best to document the new URL style without confusing people about the old style ... this is a really good start. -Hoss
[jira] Resolved: (SOLR-125) disambiguate NamedList for JSON output
[ https://issues.apache.org/jira/browse/SOLR-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley resolved SOLR-125. --- Resolution: Fixed OK, I've committed this. I wanted to get it out of the way since it touched a number of files in a minor way (keeps other patches from applying cleanly). json.nl=flat default is subjective... if people think a different default is better, let's discuss now. > disambiguate NamedList for JSON output > -- > > Key: SOLR-125 > URL: https://issues.apache.org/jira/browse/SOLR-125 > Project: Solr > Issue Type: Improvement > Components: search >Reporter: Yonik Seeley > Attachments: namedlist_json.patch > > > A NamedList implies both ordered access and access by name. For > JSON/Ruby/Python, we normally need to pick one or the other as maps are not > ordered by default in most clients. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-128) Include Newer version of Jetty
[ https://issues.apache.org/jira/browse/SOLR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468746 ] Ryan McKinley commented on SOLR-128: Ideally we could replace existing JSP with servlets or SolrRequestHandlers. I don't see anything that could not be handled using a SolrRequestHandler and default wt=xslt. For an embedded solr, it would be nice not to need the JSP dependencies. This would have the added bennefit of returning XML/JSON/ruby/etc for the admin interface. Jetty 6.1.1? where is it? Its not on: http://docs.codehaus.org/display/JETTY/Downloading+and+Installing#download > Include Newer version of Jetty > -- > > Key: SOLR-128 > URL: https://issues.apache.org/jira/browse/SOLR-128 > Project: Solr > Issue Type: Improvement > Components: update >Reporter: Ryan McKinley >Priority: Minor > Attachments: Jetty6.config.patch, lib.zip, start.jar > > > It would be good to include an up-to-date jetty version for the example. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-128) Include Newer version of Jetty
[ https://issues.apache.org/jira/browse/SOLR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468750 ] Yonik Seeley commented on SOLR-128: --- The disad to getting rid of JSPs is it would make it much harder for someone to easily improve the look or functionality of the admin pages. > Include Newer version of Jetty > -- > > Key: SOLR-128 > URL: https://issues.apache.org/jira/browse/SOLR-128 > Project: Solr > Issue Type: Improvement > Components: update >Reporter: Ryan McKinley >Priority: Minor > Attachments: Jetty6.config.patch, lib.zip, start.jar > > > It would be good to include an up-to-date jetty version for the example. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-128) Include Newer version of Jetty
[ https://issues.apache.org/jira/browse/SOLR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468749 ] Yonik Seeley commented on SOLR-128: --- When you go to the download link: http://dist.codehaus.org/jetty/ > Include Newer version of Jetty > -- > > Key: SOLR-128 > URL: https://issues.apache.org/jira/browse/SOLR-128 > Project: Solr > Issue Type: Improvement > Components: update >Reporter: Ryan McKinley >Priority: Minor > Attachments: Jetty6.config.patch, lib.zip, start.jar > > > It would be good to include an up-to-date jetty version for the example. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-84) New Solr logo?
[ https://issues.apache.org/jira/browse/SOLR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468753 ] Hoss Man commented on SOLR-84: -- I like the more muted colors and larger O size of "e" ... but i still think having a sun/O with a solid (non white) center might look better. as far as letter sizing ... i think the r really needs to be narrower -- it currently sticks outway to far to the right. the s and the r should probably either be the same height, or the s should be significantly taller (ie; capitalized) > New Solr logo? > -- > > Key: SOLR-84 > URL: https://issues.apache.org/jira/browse/SOLR-84 > Project: Solr > Issue Type: Improvement >Reporter: Bertrand Delacretaz >Priority: Minor > Attachments: logo-solr-d.jpg, logo-solr-e.jpg, > logo-solr-source-files-take2.zip, solr-84-source-files.zip, > solr-logo-20061214.jpg, solr-logo-20061218.JPG, solr-logo-20070124.JPG, > solr.jpg, solr.jpg > > > Following up on SOLR-76, our trainee Nicolas Barbay (nicolas (put at here) > sarraux-dessous.ch) has reworked his logo proposal to be more "solar". > This can either be the start of a logo contest, or if people like it we could > adopt it. The gradients can make it a bit hard to integrate, not sure if this > is really a problem. > WDYT? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (SOLR-128) Include Newer version of Jetty
: : The disad to getting rid of JSPs is it would make it much harder for : someone to easily improve the look or functionality of the admin pages. "look" could be improved with XSLT in most cases yes/no? ... as for functionality ... it's not like we are leveraging a lot of JSP code siplcations -- we dont' have extensive taglibs or anything making our JSPs easy for novices to understand -- you pretty much have to know Java to change them right now, and you have to have a JDK installed on our box to test your JSP changes ... so why not make them RequestHandlers? -Hoss
[jira] Commented: (SOLR-128) Include Newer version of Jetty
[ https://issues.apache.org/jira/browse/SOLR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468758 ] Ryan McKinley commented on SOLR-128: I'm not suggesting we drop JSP *now*... just that we definitely should not be using 2.1 specific stuff and where possible xml+xslt with a RequestHandler (SOLR-58) in the future. I just tried this with 6.1.1 and it works fine (with the jsp-2.0 or jsp-2.1) What is the best way for me to post this patch? Most of the work is adding and deleting jar files. It has two xml config files etc/jetty.xml and etc/webdefault.xml > Include Newer version of Jetty > -- > > Key: SOLR-128 > URL: https://issues.apache.org/jira/browse/SOLR-128 > Project: Solr > Issue Type: Improvement > Components: update >Reporter: Ryan McKinley >Priority: Minor > Attachments: Jetty6.config.patch, lib.zip, start.jar > > > It would be good to include an up-to-date jetty version for the example. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-84) New Solr logo?
[ https://issues.apache.org/jira/browse/SOLR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468761 ] Yonik Seeley commented on SOLR-84: -- FWIW, I like the shining/rays effect of "d" and "e". > New Solr logo? > -- > > Key: SOLR-84 > URL: https://issues.apache.org/jira/browse/SOLR-84 > Project: Solr > Issue Type: Improvement >Reporter: Bertrand Delacretaz >Priority: Minor > Attachments: logo-solr-d.jpg, logo-solr-e.jpg, > logo-solr-source-files-take2.zip, solr-84-source-files.zip, > solr-logo-20061214.jpg, solr-logo-20061218.JPG, solr-logo-20070124.JPG, > solr.jpg, solr.jpg > > > Following up on SOLR-76, our trainee Nicolas Barbay (nicolas (put at here) > sarraux-dessous.ch) has reworked his logo proposal to be more "solar". > This can either be the start of a logo contest, or if people like it we could > adopt it. The gradients can make it a bit hard to integrate, not sure if this > is really a problem. > WDYT? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
loading many documents by ID
I am working on an SQLUpdatePlugin that needs to set a few fields in the document and leave the rest as they were. My plan is to load the old documents from the current searcher and overwrite any fields set from SQL. What is the best way to load a (potentially) large set of documents by ID? Should I make one query with a list of all IDs? make a separate query for each ID? Is there a cache i can try to pull them from? thanks for any pointers. ryan
SOLR Improvement: Expiration
If it is not implemented/reported yet... I am having problems with deleting of old documents, would be nice to have default expiration policy! Thanks
Re: SOLR Improvement: Expiration
On 1/30/07 5:07 PM, "Fuad Efendi" <[EMAIL PROTECTED]> wrote: > If it is not implemented/reported yet... > I am having problems with deleting of old documents, would be nice to have > default expiration policy! Building in some specific policy would be hard and only useful for people with exactly that problem. Instead, include a date field and delete by query. No features needed, just a tiny bit of client code. wunder
Re: SOLR Improvement: Expiration
you can add a date field to your schema with a default value "NOW". This will give each document a timestamp for when it was indexed. I have this in my schema: then you can easily delete with a query. On 1/30/07, Fuad Efendi <[EMAIL PROTECTED]> wrote: If it is not implemented/reported yet... I am having problems with deleting of old documents, would be nice to have default expiration policy! Thanks
RE: SOLR Improvement: Expiration
Thanks! Curently I submit about 100 delete requests per second... Using your SolrEx! -Original Message- From: Ryan McKinley= you can add a date field to your schema with a default value "NOW". This will give each document a timestamp for when it was indexed. I have this in my schema: then you can easily delete with a query.
Re: loading many documents by ID
On 1/30/07, Ryan McKinley <[EMAIL PROTECTED]> wrote: I am working on an SQLUpdatePlugin that needs to set a few fields in the document and leave the rest as they were. My plan is to load the old documents from the current searcher and overwrite any fields set from SQL. What is the best way to load a (potentially) large set of documents by ID? Should I make one query with a list of all IDs? make a separate query for each ID? Is there a cache i can try to pull them from? See SolrIndexSearcher: public int getFirstMatch(Term t) throws IOException That returns an internal lucene docid for the first match of a term (make sure to convert it to internal form first via FieldType.toInternal() Then use SolrIndexSearcher.doc(int) to get the document (it will check the cache). Trying to retrieve multiple at once doesn't offer a performance benefit as Lucene needs to seek to each term anyway. -Yonik
Re: loading many documents by ID
On 1/30/07, Ryan McKinley <[EMAIL PROTECTED]> wrote: I am working on an SQLUpdatePlugin that needs to set a few fields in the document and leave the rest as they were. Oh, and there have been numerous people interested in "updateable" documents, so it would be nice if that part was in the update handler. -Yonik
