Re: [jira] Created: (SOLR-1363) Search without using caches

Keep in mind that there is no way to bypass the most important cache of all (os disk cache). -Mike On Thu, Aug 13, 2009 at 12:01 PM, Jason Rutherglen (JIRA) wrote: > > For testing, I often need to perform a query and see the actual time it > takes (rather than the time it takes to look it up from

Re: [jira] Updated: (SOLR-1155) Change DirectUpdateHandler2 to allow concurrent adds during an autocommit

I'd like to take a look at this but JIRA seems to be down. Is anyone else experiencing this? -Mike On Wed, May 13, 2009 at 7:41 AM, Jayson Minard (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/SOLR-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] > > Jays

[jira] Commented: (SOLR-1169) SortedIntDocSet

[ https://issues.apache.org/jira/browse/SOLR-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709645#action_12709645 ] Mike Klaas commented on SOLR-1169: -- sweet. intersecting sorted int dicts should be fa

Re: DirectUpdateHandler2 threads pile up behind scheduleCommitWithin

Lucene behavior. https://issues.apache.org/jira/browse/SOLR-1155 --j Mike Klaas wrote: On 7-May-09, at 10:36 AM, jayson.minard wrote: Does every thread really need to notify the update handler of the commit interval/threshold being reached, or really just the first thread that notices should

Re: DirectUpdateHandler2 threads pile up behind scheduleCommitWithin

On 7-May-09, at 10:36 AM, jayson.minard wrote: Does every thread really need to notify the update handler of the commit interval/threshold being reached, or really just the first thread that notices should send the signal, or better yet a background commit watching thread so that no "foreg

Re: Welcome new Solr committers Mark Miller and Noble Paul

On 30-Apr-09, at 10:41 AM, Yonik Seeley wrote: I'm pleased to announce that Mark Miller and Noble Paul have accepted invitations to become Solr committers! Welcome Mark & Noble, and thanks for all your great work on Solr! Congratulations Mark and Noble! Good to have you on board. -Mike

[jira] Commented: (SOLR-1116) Add a Binary FieldType

[ https://issues.apache.org/jira/browse/SOLR-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12704284#action_12704284 ] Mike Klaas commented on SOLR-1116: -- +1 for url-safe base64 (-_ being the extra c

[jira] Commented: (SOLR-1044) Use Hadoop RPC for inter Solr communication

[ https://issues.apache.org/jira/browse/SOLR-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679466#action_12679466 ] Mike Klaas commented on SOLR-1044: -- {quote} I haven't yet seen a HTTP server ser

[jira] Commented: (SOLR-952) duplicated code in (Default)SolrHighlighter and HighlightingUtils

[ https://issues.apache.org/jira/browse/SOLR-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674830#action_12674830 ] Mike Klaas commented on SOLR-952: - HighlightingUtils has been deprecated for at least

Re: [jira] Commented: (SOLR-912) org.apache.solr.common.util.NamedList - Typesafe efficient variant - ModernNamedList introduced - implementing the same API as NamedList

On 19-Dec-08, at 8:27 AM, Kay Kay (JIRA) wrote: Meanwhile - w.r.t resize() - ( trade-off because increasing size a lot would increase memory usage. increase a size by a smaller factor would be resulting in a more frequent increases in size). I believe reading some theory that the ideal i

Re: [VOTE] LOGO

The logo is now up! http://lucene.apache.org/solr/ Thanks to Hoss who fixed a missing file check in. The one thing not caught by testing locally... -Mike On 19-Dec-08, at 12:52 PM, Ryan McKinley wrote: go for it (i don't have forrest running...) On Dec 19, 2008, at 3:34 PM,

Re: [VOTE] LOGO

On 17-Dec-08, at 5:11 PM, Ryan McKinley wrote: Hoss - can you go ahead and post something? I'm heading out... but could post tomorrow. Since the community has been notified, any objections to me updating the site with the new logo/favicon? -Mike

Re: [VOTE] LOGO

On 13-Dec-08, at 2:52 PM, Ryan McKinley wrote: Ok, all votes are cast (except Grant who is abstaining) Thanks for tallying the votes, Ryan. You're too damn quick for me! -Mike

Re: [VOTE] LOGO

https://issues.apache.org/jira/secure/attachment/12394264/apache_solr_a_red.jpg https://issues.apache.org/jira/secure/attachment/12394268/apache_solr_c_red.jpg https://issues.apache.org/jira/secure/attachment/12394070/sslogo-solr-finder2.0.png https://issues.apache.org/jira/secure/attachment/12394

Re: [VOTE] LOGO

I agree. I don't see why there needs to be a minimum or maximum number of logos to rank per vote. -Mike On 10-Dec-08, at 7:52 PM, Yonik Seeley wrote: Doesn't limiting to top 4 defeat the purpose of using STV to overcome splitting-the-vote? Seems like we should rank the whole list (or all t

Re: logo contest

On 10-Dec-08, at 12:41 PM, Yonik Seeley wrote: Sure thing. I take it that there are no objections? If so, I'll call a vote by the end of the week. +1 I just wish we had used this method with the community vote. I guess as a committer I should try and figure out what order the community

Re: logo contest

On 8-Dec-08, at 10:47 AM, Mike Klaas wrote: On 7-Dec-08, at 7:40 PM, Chris Hostetter wrote: : I would personally prefer more of an "elimination"-style vote (i.e., STV). Ah... yeah, that seems like it would be a more fair way to deal with things then my suggestion, and it doesn

Re: logo contest

On 7-Dec-08, at 7:40 PM, Chris Hostetter wrote: : I would personally prefer more of an "elimination"-style vote (i.e., STV). Ah... yeah, that seems like it would be a more fair way to deal with things then my suggestion, and it doesn't violate the spirt of the rules as original outlined (it

Re: logo contest

On 4-Dec-08, at 2:33 PM, Chris Hostetter wrote: : Being the likely two candidates for winning. My guess is that : narrowing to the two most popular options first would make #2 the : winner, while voting on the top 10 (w/o any strategy for winning) : would make #1 the winner. limiting to only

Optimizing range constraints

Tim Sturge posted a nice optimization for range constraints/filters (e.g. "age:[10 TO 35]") here: https://issues.apache.org/jira/browse/LUCENE-1461 It has a natural applicability to Solr's fq range filters, which can be abysmally slow for large ranges. Could be an interesting project for

Re: Deadlock with DirectUpdateHandler2

On 18-Nov-08, at 8:54 AM, Mark Miller wrote: Mark Miller wrote: Toby Cole wrote: Has anyone else experienced a deadlock when the DirectUpdateHandler2 does an autocommit? I'm using a recent snapshot from hudson (apache- solr-2008-11-12_08-06-21), and quite often when I'm loading data the s

Re: [jira] Commented: (SOLR-84) Logo Contests

On 14-Nov-08, at 8:54 AM, Doug Cutting (JIRA) wrote: [ https://issues.apache.org/jira/browse/SOLR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647660 #action_12647660 ] Doug Cutting commented on SOLR-84: -- I

Re: ReentrantReadWriteLock in DUH2

On 6-Nov-08, at 7:48 AM, Koji Sekiguchi wrote: > So that multiple threads can efficiently access the writer, but only one thread at a time does a commit. > Adding docs with the writer is the 'read' and committing is the write. If I remember correctly. You remember correctly, Mark. Because

[jira] Commented: (SOLR-793) set a commit time bounds in the command

[ https://issues.apache.org/jira/browse/SOLR-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638825#action_12638825 ] Mike Klaas commented on SOLR-793: - I don't see any issue with the code: adddedDo

[jira] Commented: (SOLR-793) set a commit time bounds in the command

[ https://issues.apache.org/jira/browse/SOLR-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637173#action_12637173 ] Mike Klaas commented on SOLR-793: - Hey Ryan, I think this is good functionality and

Re: Setting Fix Version in JIRA

On 23-Sep-08, at 12:33 PM, Otis Gospodnetic wrote: Hi, When people add new issues to JIRA they most often don't set the "Fix Version" field. Would it not be better to have a default value for that field, so that new entries don't get forgotten when we filter by "Fix Version" looking for

Re: Solr 1.3.0 Release Lessons Learned

On 22-Sep-08, at 10:34 AM, Shalin Shekhar Mangar wrote: I'd like to propose a more pro-active approach to release planning by the community. At any given time, let's have two versions in JIRA. Only those issues which a committer has assigned to himself should be in the first un-released

[jira] Commented: (SOLR-777) backword match search, for domain search etc.

[ https://issues.apache.org/jira/browse/SOLR-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632842#action_12632842 ] Mike Klaas commented on SOLR-777: - As Walter mentioned, you don't really want rever

Re: 1.3.0 + Woodstox

Thanks, it has been closed now. -Mike On 11-Sep-08, at 11:06 AM, Grant Ingersoll wrote: Note, SOLR-766 is still open. On Sep 11, 2008, at 1:23 PM, Grant Ingersoll wrote: http://people.apache.org/~gsingers/solr/1.3.0/ Give it a try. -Grant

[jira] Resolved: (SOLR-766) Remove python client from 1.3 distribution

[ https://issues.apache.org/jira/browse/SOLR-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas resolved SOLR-766. - Resolution: Fixed > Remove python client from 1.3 distribut

[jira] Updated: (SOLR-766) Remove python client from 1.3 distribution

[ https://issues.apache.org/jira/browse/SOLR-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas updated SOLR-766: Attachment: SOLR-766.patch > Remove python client from 1.3 distribut

[jira] Commented: (SOLR-766) Remove python client from 1.3 distribution

[ https://issues.apache.org/jira/browse/SOLR-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630004#action_12630004 ] Mike Klaas commented on SOLR-766: - JIRA seems to be not allowing me to upload a patch.

[jira] Created: (SOLR-766) Remove python client from 1.3 distribution

Versions: 1.3 Reporter: Mike Klaas Assignee: Mike Klaas Priority: Blocker Fix For: 1.3 see solr-dev thread: http://mail-archives.apache.org/mod_mbox/lucene-solr-dev/200809.mbox/[EMAIL PROTECTED] -- This message is automatically generated by JIRA

[jira] Commented: (SOLR-216) Improvements to solr.py

[ https://issues.apache.org/jira/browse/SOLR-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629981#action_12629981 ] Mike Klaas commented on SOLR-216: - That's great! Be sure to update http://wiki.a

Re: solr.py [was: license headers]

On 9-Sep-08, at 6:49 PM, Chris Hostetter wrote: : I was thinking that we may want to move the python client out of the distro as : well. It is untested with 1.3 and unmaintained. +1 that seems like the best plan. I would make a note to that effect in both a new client/python/README.tx

solr.py [was: license headers]

I was thinking that we may want to move the python client out of the distro as well. It is untested with 1.3 and unmaintained. Is seems that it would be best for an interested party to maintain a python client outside the confines of the official Solr project (we can always re-integrate it

[jira] Commented: (SOLR-216) Improvements to solr.py

[ https://issues.apache.org/jira/browse/SOLR-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629556#action_12629556 ] Mike Klaas commented on SOLR-216: - Dariusz, Have you thought about publishing the up

Re: Solr's use of Lucene's Compression field

avoid relying on a deprecated lucene feature that isn't well exercised in development. -Mike On 3-Sep-08, at 11:36 AM, Mike Klaas wrote: Agreed. It was the simplest thing to do at the time, but it would definitely be preferrable to offer the much faster lesser levels of compression.

Re: Solr's use of Lucene's Compression field

Agreed. It was the simplest thing to do at the time, but it would definitely be preferrable to offer the much faster lesser levels of compression. -Mike On 3-Sep-08, at 8:57 AM, Grant Ingersoll wrote: Thinking about http://lucene.markmail.org/message/mef4cdo7m3s6i3fc?q=background+merge+exc

[jira] Commented: (SOLR-684) Hudson builds do not have the SVN revision because svnversion is not available

[ https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627106#action_12627106 ] Mike Klaas commented on SOLR-684: - Good point, Hoss. > Hudson builds do not have

[jira] Commented: (SOLR-684) Hudson builds do not have the SVN revision because svnversion is not available

[ https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627090#action_12627090 ] Mike Klaas commented on SOLR-684: - In case this ever needs to be done with pure

[jira] Commented: (SOLR-739) Add support for OmitTf

[ https://issues.apache.org/jira/browse/SOLR-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627049#action_12627049 ] Mike Klaas commented on SOLR-739: - Haven't looked at the patch, but defaulting

Re: 1.3 status

+1 for 1.3 RC. The idea of putting new issues in 1.3.1 has been tossed around a few times on this list in the last few weeks. I'm not sure how other people feel about this, but in my mind, 1.X.Y and 1.X.Z releases should be feature-identical, with later releases only containing bugfixes

[jira] Resolved: (SOLR-474) audit docs for Spellchecker

[ https://issues.apache.org/jira/browse/SOLR-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas resolved SOLR-474. - Resolution: Fixed I've verified the behaviour and updated the wiki page accordingly. > audit

[jira] Commented: (SOLR-474) audit docs for Spellchecker

[ https://issues.apache.org/jira/browse/SOLR-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622677#action_12622677 ] Mike Klaas commented on SOLR-474: - The issue is more wikidocs vs. behaviour. I apologi

[jira] Commented: (SOLR-216) Improvements to solr.py

[ https://issues.apache.org/jira/browse/SOLR-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622391#action_12622391 ] Mike Klaas commented on SOLR-216: - Hi Dariusz, There will almost certainly be no

Re: AutoCommitTest

On 5-Aug-08, at 3:32 PM, Yonik Seeley wrote: AutoCommitTest was failing for me a good percentage of the time... the comment suggested that adding another doc after the commit callback would block until the new searcher was registered. But that's not the case. I've hacked the test for now to ju

Re: ClientUtils escape query

Wouldn't you want to reverse all escaping in that case anyway? -Mike On 5-Aug-08, at 1:45 PM, Grant Ingersoll wrote: It's mainly a problem when one wants to display the thing later, I guess. -Grant On Aug 5, 2008, at 4:16 PM, Ryan McKinley wrote: That came after I spent a week increasing

[jira] Updated: (SOLR-659) Explicitly set start and rows per shard for more efficient bulk queries across distributed Solr

[ https://issues.apache.org/jira/browse/SOLR-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas updated SOLR-659: Fix Version/s: (was: 1.3) IMO it is too late in the release process for new features. > Explicitly

Re: [jira] Issue Comment Edited: (SOLR-665) FIFO Cache (Unsynchronized): 9x times performance boost

On 29-Jul-08, at 3:20 AM, Andrew Savory wrote: Actually I'd argue that all such technical discussion would be better done on the mailing list rather than through JIRA. Mail clients are designed for threaded discussions far better than JIRA's web GUI. And JIRA's posting back to the list with bq.

[jira] Commented: (SOLR-474) audit docs for Spellchecker

[ https://issues.apache.org/jira/browse/SOLR-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617580#action_12617580 ] Mike Klaas commented on SOLR-474: - I will look at this before release. > audit d

[jira] Commented: (SOLR-665) FIFO Cache (Unsynchronized): 9x times performance boost

[ https://issues.apache.org/jira/browse/SOLR-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617549#action_12617549 ] Mike Klaas commented on SOLR-665: - [quote]We may simply use java.util.concurrent.l

[jira] Commented: (SOLR-665) FIFO Cache (Unsynchronized): 9x times performance boost

[ https://issues.apache.org/jira/browse/SOLR-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617512#action_12617512 ] Mike Klaas commented on SOLR-665: - I haven't looked at the proposed code at all, bu

[jira] Commented: (SOLR-139) Support updateable/modifiable documents

[ https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616729#action_12616729 ] Mike Klaas commented on SOLR-139: - [quote]David - storing all data in the search index

Re: Defining properties/using expressions in {multicore, config, schema} files

On 21-Jul-08, at 10:48 AM, Henrib wrote: I posted a new patch in solr-350 (solr-350-properties.patch) that allows defining properties in multicore.xml and using them in expressions in config & schema files. This brings a lot of flexibility to configuration. I apologize for doubling the J

Re: Welcom Shalin Shekhar Mangar

Welcome aboard, Shalin! -Mike On 19-Jul-08, at 12:01 PM, Shalin Shekhar Mangar wrote: Thanks! I work at AOL in Bangalore as part of a small team which gets to work on a variety of (very cool!) stuff. Though my involvement started when we decided to contribute part of our work to Solr (Dat

[jira] Assigned: (SOLR-610) Add support for hl.maxAnalyzedChars=-1 to highlight the whole field

[ https://issues.apache.org/jira/browse/SOLR-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas reassigned SOLR-610: --- Assignee: Mike Klaas > Add support for hl.maxAnalyzedChars=-1 to highlight the whole fi

[jira] Resolved: (SOLR-610) Add support for hl.maxAnalyzedChars=-1 to highlight the whole field

[ https://issues.apache.org/jira/browse/SOLR-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas resolved SOLR-610. - Resolution: Fixed commited. Thanks lars! > Add support for hl.maxAnalyzedChars=-1 to highlight the wh

[jira] Resolved: (SOLR-556) Highlighting of multi-valued fields returns snippets which span multiple different values

[ https://issues.apache.org/jira/browse/SOLR-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas resolved SOLR-556. - Resolution: Fixed committed as part of SOLR-610. thanks Lars! > Highlighting of multi-valued fie

[jira] Updated: (SOLR-610) Add support for hl.maxAnalyzedChars=-1 to highlight the whole field

[ https://issues.apache.org/jira/browse/SOLR-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas updated SOLR-610: Fix Version/s: 1.3 > Add support for hl.maxAnalyzedChars=-1 to highlight the whole fi

[jira] Commented: (SOLR-610) Add support for hl.maxAnalyzedChars=-1 to highlight the whole field

[ https://issues.apache.org/jira/browse/SOLR-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608878#action_12608878 ] Mike Klaas commented on SOLR-610: - Hi Lars, I was planning on commiting SOLR-556. W

Re: XSS in Solr admin interface

On 19-Jun-08, at 11:17 PM, Nicob wrote: Le jeudi 19 juin 2008 à 19:21 -0700, Mike Klaas a écrit : Fixed in r669766. I checked the patch and it's correctly patching this XSS. Thanks to the dev team ! Thanks for the report! -Mike

Re: XSS in Solr admin interface

On 19-Jun-08, at 5:47 PM, Yonik Seeley wrote: On Thu, Jun 19, 2008 at 7:42 PM, Nicob <[EMAIL PROTECTED]> wrote: while testing the Solr search engine, I found a XSS vulnerability in its administration interface. I wrote to [EMAIL PROTECTED], but I wonder if this list could be a better place

[jira] Commented: (SOLR-14) Add the ability to preserve the original term when using WordDelimiterFilter

[ https://issues.apache.org/jira/browse/SOLR-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605410#action_12605410 ] Mike Klaas commented on SOLR-14: Also, voting for an issue is a good way to increase

[jira] Commented: (SOLR-14) Add the ability to preserve the original term when using WordDelimiterFilter

[ https://issues.apache.org/jira/browse/SOLR-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605403#action_12605403 ] Mike Klaas commented on SOLR-14: Note that it is very easy to use an external TokenFilter

[jira] Commented: (SOLR-556) Highlighting of multi-valued fields returns snippets which span multiple different values

[ https://issues.apache.org/jira/browse/SOLR-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603785#action_12603785 ] Mike Klaas commented on SOLR-556: - Hey Lars, Yeah, I'm talking about highlightin

[jira] Commented: (SOLR-556) Highlighting of multi-valued fields returns snippets which span multiple different values

[ https://issues.apache.org/jira/browse/SOLR-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603780#action_12603780 ] Mike Klaas commented on SOLR-556: - Thanks for the patch, Lars. I think that the b

Re: Solr Maven Artifacts

As someone who is completely ignorant (and admittedly, somewhat willfully so) of the java enterprise world, I was hoping that someone more savvy in the ways of maven would step in here. It is even unclear to me what having the project in a Maven repository means for people, or why it would

Re: [jira] Commented: (SOLR-560) Convert JDK logging to SLF4J

On 5-Jun-08, at 6:42 PM, Ryan McKinley (JIRA) wrote: Ryan McKinley commented on SOLR-560: I removed this from the 1.3 list... Hopefully we can add it just after the 1.3 release so we have plenty of time to know if it is an ok choice. Oh, thanks. I don

Re: [important] call for 1.3 planning

On 21-May-08, at 4:45 PM, Mike Klaas wrote: There seems to be some sort of consensus building that there should be a 1.3 release in the near future. The first step is to figure out what we want to finish before it gets released. The list of JIRA issues currently labeled 1.3 can be found

[jira] Commented: (SOLR-243) Create a hook to allow custom code to create custom IndexReaders

[ https://issues.apache.org/jira/browse/SOLR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602860#action_12602860 ] Mike Klaas commented on SOLR-243: - Hi John, Hoss has marked the issue for 1.3, so it

[jira] Updated: (SOLR-522) analysis.jsp doesn't show payloads created/modified by tokenizers and tokenfilters

[ https://issues.apache.org/jira/browse/SOLR-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas updated SOLR-522: Fix Version/s: 1.3 > analysis.jsp doesn't show payloads created/modified by tokenizers and > t

[jira] Commented: (SOLR-517) highlighter doesn't work with hl.requireFieldMatch=true on un-optimized index

[ https://issues.apache.org/jira/browse/SOLR-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602857#action_12602857 ] Mike Klaas commented on SOLR-517: - Koji: Is this resolved? I seemed to recall tha

[jira] Closed: (SOLR-460) Improvement to highlighting infrastructure

[ https://issues.apache.org/jira/browse/SOLR-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas closed SOLR-460. --- Resolution: Won't Fix No patch, breaks backward compatibility > Improvement to highlighting infras

[jira] Assigned: (SOLR-522) analysis.jsp doesn't show payloads created/modified by tokenizers and tokenfilters

[ https://issues.apache.org/jira/browse/SOLR-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas reassigned SOLR-522: --- Assignee: Mike Klaas > analysis.jsp doesn't show payloads created/modified by tokeni

[jira] Resolved: (SOLR-200) Scripts don't work when run as root in ~root and su'ing to a user

[ https://issues.apache.org/jira/browse/SOLR-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas resolved SOLR-200. - Resolution: Won't Fix It doesn't surprise me that "/root" as the indexdir and "

[jira] Closed: (SOLR-344) New Java API

[ https://issues.apache.org/jira/browse/SOLR-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas closed SOLR-344. --- Resolution: Invalid Let's move this discussion to the wiki and mailinglist. It isn't really an &

[jira] Updated: (SOLR-424) The ruby output type produces incorrect output for numeric types without a value

[ https://issues.apache.org/jira/browse/SOLR-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas updated SOLR-424: Eric or Yonik, do you want to mentor this for 1.3? > The ruby output type produces incorrect output for nume

[jira] Assigned: (SOLR-489) Added @deprecation Javadoc comments

[ https://issues.apache.org/jira/browse/SOLR-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas reassigned SOLR-489: --- Assignee: Mike Klaas > Added @deprecation Javadoc comme

[jira] Assigned: (SOLR-545) remove MultiCore "default" core / cleanup DispatchHandlera

[ https://issues.apache.org/jira/browse/SOLR-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas reassigned SOLR-545: --- Assignee: Ryan McKinley assigning 1.3 multicore stuff to Ryan > remove MultiCore "defau

[jira] Assigned: (SOLR-560) Convert JDK logging to SLF4J

[ https://issues.apache.org/jira/browse/SOLR-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas reassigned SOLR-560: --- Assignee: Ryan McKinley It's Ryan's patch. > Convert JDK log

[jira] Updated: (SOLR-243) Create a hook to allow custom code to create custom IndexReaders

[ https://issues.apache.org/jira/browse/SOLR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas updated SOLR-243: Do we still want to target 1.3 here? (Seems like there is a lot to do before it is commit-worthy, based on the

[jira] Commented: (SOLR-410) Audit the new ResponseBuilder class

[ https://issues.apache.org/jira/browse/SOLR-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602834#action_12602834 ] Mike Klaas commented on SOLR-410: - Ryan, can this be closed? > Audit

[jira] Updated: (SOLR-84) New Solr logo?

[ https://issues.apache.org/jira/browse/SOLR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas updated SOLR-84: --- Fix Version/s: (was: 1.3) > New Solr logo? > -- > >

[jira] Updated: (SOLR-484) Solr Website changes

[ https://issues.apache.org/jira/browse/SOLR-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas updated SOLR-484: Fix Version/s: (was: 1.3) > Solr Website changes > > >

[jira] Updated: (SOLR-284) Parsing Rich Document Types

[ https://issues.apache.org/jira/browse/SOLR-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas updated SOLR-284: Fix Version/s: (was: 1.3) > Parsing Rich Document Ty

[jira] Updated: (SOLR-351) external value source

[ https://issues.apache.org/jira/browse/SOLR-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas updated SOLR-351: Fix Version/s: (was: 1.3) > external value source > - > >

[jira] Updated: (SOLR-433) MultiCore and SpellChecker replication

[ https://issues.apache.org/jira/browse/SOLR-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas updated SOLR-433: Fix Version/s: (was: 1.3) > MultiCore and SpellChecker replicat

[jira] Updated: (SOLR-435) QParser must validate existance/absense of "q" parameter

[ https://issues.apache.org/jira/browse/SOLR-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas updated SOLR-435: Fix Version/s: (was: 1.3) > QParser must validate existance/absense of "q&qu

[jira] Updated: (SOLR-284) Parsing Rich Document Types

[ https://issues.apache.org/jira/browse/SOLR-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas updated SOLR-284: Affects Version/s: (was: 1.3) Removing from 1.3. No committer has taken ownership. (It might make

[jira] Commented: (SOLR-572) Spell Checker as a Search Component

[ https://issues.apache.org/jira/browse/SOLR-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602828#action_12602828 ] Mike Klaas commented on SOLR-572: - [quote]Another use case is where Solr is used

[jira] Commented: (SOLR-536) Automatic binding of results to Beans (for solrj)

[ https://issues.apache.org/jira/browse/SOLR-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602744#action_12602744 ] Mike Klaas commented on SOLR-536: - > This is expensive > private final Map&

[jira] Commented: (SOLR-556) Highlighting of multi-valued fields returns snippets which span multiple different values

[ https://issues.apache.org/jira/browse/SOLR-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602541#action_12602541 ] Mike Klaas commented on SOLR-556: - Ah, I see what the problem is: Although it is imposs

Re: 3 TokenFilter factories not compatible with 1.2

On 4-Jun-08, at 5:24 PM, Yonik Seeley wrote: On Wed, Jun 4, 2008 at 7:03 PM, Chris Hostetter <[EMAIL PROTECTED]> wrote: 3) Documentation and Education Since this wasn't exactly a use case we ever advertised, we could punt on the problem by putting a disclaimer in the CAHNGES.txt that ayone

[jira] Commented: (SOLR-161) Dangling dash causes stack trace

[ https://issues.apache.org/jira/browse/SOLR-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602038#action_12602038 ] Mike Klaas commented on SOLR-161: - > It is really a Lucene query parser bug, but it w

Re: Release of SOLR 1.3

On 20-May-08, at 12:32 PM, Shalin Shekhar Mangar wrote: +1 for your suggestions Mike. I'd like to see a few of the smaller issues get committed in 1.3 such as SOLR-256 (JMX), SOLR-536 (binding for SolrJ), SOLR-430 (SpellChecker support in SolrJ) etc. Also, SOLR-561 (replication by Solr) wo

Re: Release of SOLR 1.3

On 22-May-08, at 12:13 AM, Andrew Savory wrote: Sure, Commit-Then-Review vs. Review-Then-Commit ... but I don't actually think RTC is going to ensure significantly more widespread review since the time burden on other developers to find the issue in JIRA, download the patch, apply the patch, te

[jira] Updated: (SOLR-583) Name Service

[ https://issues.apache.org/jira/browse/SOLR-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Klaas updated SOLR-583: Fix Version/s: (was: 1.3) > Name Service > > > K

[jira] Commented: (SOLR-583) Name Service

[ https://issues.apache.org/jira/browse/SOLR-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598880#action_12598880 ] Mike Klaas commented on SOLR-583: - Jason, it would be better to hash out ideas/fu

[important] call for 1.3 planning

There seems to be some sort of consensus building that there should be a 1.3 release in the near future. The first step is to figure out what we want to finish before it gets released. The list of JIRA issues currently labeled 1.3 can be found here:

  1   2   3   4   5   6   >