: Improvement
Components: search
Affects Versions: 1.3
Reporter: Erik Hatcher
Assignee: Erik Hatcher
Priority: Minor
Fix For: 1.3
IndexSchema is currently tied to reading a file system schema.xml file. In
order to more dynamically
[
https://issues.apache.org/jira/browse/SOLR-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549029
]
Erik Hatcher commented on SOLR-427:
---
Ultimately what I want to do is affect an in-memory schema and then load a new
[
https://issues.apache.org/jira/browse/SOLR-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher resolved SOLR-411.
---
Resolution: Fixed
Fix Version/s: 1.3
Thanks Grant!
Solr JAR Packaging Names
anybody compared/contrasted the two? seems like yonik's noggit
parser might have a performance edge on xml parsing ?!
Erik
Issue Type: Bug
Components: clients - ruby - flare
Reporter: Erik Hatcher
Assignee: Erik Hatcher
There is an issue with the ruby response (and others too, perhaps json and
python) when an integer field is sent with leading zeros. For example (from
[
https://issues.apache.org/jira/browse/SOLR-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher updated SOLR-394:
--
Description:
There is an issue with the ruby response (and others too, perhaps json and
python) when
Done. That one had just bitten me with compilation issues while
setting up a new IDE project with IntelliJ 7.
Erik
On Oct 25, 2007, at 11:04 AM, Ryan McKinley wrote:
Bill Au wrote:
Subject says it all.
+1
[
https://issues.apache.org/jira/browse/SOLR-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535489
]
Erik Hatcher commented on SOLR-380:
---
The idea was to use dynamic fields (e.g. page_1, page_2, page_3... page_N
Reporter: Erik Hatcher
Priority: Minor
Reported by Rob Casson:
indexing the example docs from 1.2, these steps work:
curl http://localhost:8983/solr/update --data-binary
'deletequerysolr/query/delete' -H 'Content-type:text/xml;
charset=utf-8'
curl http://localhost:8983
[
https://issues.apache.org/jira/browse/SOLR-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher updated SOLR-127:
--
Fix Version/s: 1.3
targeting this for the 1.3 release.
Make Solr more friendly to external HTTP caches
[
https://issues.apache.org/jira/browse/SOLR-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher resolved SOLR-359.
---
Resolution: Fixed
Patch applied, thanks!
Luke keeps getting handier and handier.
I also agree
[
https://issues.apache.org/jira/browse/SOLR-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher resolved SOLR-154.
---
Resolution: Fixed
I've been using the Rails gem packaging feature in solr-ruby's trunk for a
while
[
https://issues.apache.org/jira/browse/SOLR-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher resolved SOLR-362.
---
Resolution: Fixed
Fix Version/s: 1.3
Assignee: Erik Hatcher
Thanks Thorsten!
bundle
On Sep 19, 2007, at 5:52 PM, Chris Hostetter wrote:
Everybody i've ever talked to who i felt confident knew more about ant
then me (with Erik at teh top of the list) has said the same thing:
Put
junit and ant-junit in your ANT_LIB ... don't even try to do anything
else, it will just burn
On Sep 20, 2007, at 12:13 PM, Thorsten Scherler wrote:
On Wed, 2007-09-19 at 16:33 -0400, Ryan McKinley wrote:
Yonik Seeley wrote:
ant test from the command line is currently failing.
compileTests:
[mkdir] Created dir: F:\code\solr\build\tests
[javac] Compiling 66 source files to
On Sep 20, 2007, at 1:51 PM, Erik Hatcher wrote:
IMHO ivy rocks and would perfectly overcome this problem without
cluttering the build files with jar versions.
I'm happy to see contributions both for Ivy and Maven2 based builds
of Solr. I'm sure we can do it in a non-intrusive way
- flare
Reporter: Erik Hatcher
Assignee: Erik Hatcher
Fix For: 1.3
Implement solr-ruby-specific Ruby output, such that dates get created as real
DateTime objects (wrap with DateTime.parse(...) is one option), and so that
named lists maintain name and order
Ryan,
Since the QueryParser can handle any character being escaped, I just
escaped every non-alphanumeric character on the solr-ruby side of
things.
http://svn.apache.org/viewvc/lucene/solr/trunk/client/ruby/solr-
ruby/lib/solr/util.rb?view=markup
Playing keep up with any changes to
[
https://issues.apache.org/jira/browse/SOLR-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527337
]
Erik Hatcher commented on SOLR-127:
---
What about etags? http://intertwingly.net/blog/2006/06/05/Elevator-Pitch
I'm open to letting other build systems flourish if folks want them.
As long as I can svn co and build Solr without too much hassle
(other than installing a build tool and a JDK) I'm happy :)
There is a contingent of Maven freaks in the Lucene world these days,
and Lucene is getting
On Sep 6, 2007, at 10:25 PM, Chris Hostetter wrote:
: Kinda cute, but not worth starting a revolution about. Structure is
: overrated.
you mean you aren't going to make the build fail if the CHANGES.yml
file
can't be parsed? :)
Now there's an idea! Committed a unit test for this. Need
[
https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher updated SOLR-139:
--
Attachment: Eriks-ModifiableDocument.patch
For posterity, here's the patch I'm running in Collex
[
https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522310
]
ehatcher edited comment on SOLR-139 at 8/23/07 4:59 PM:
There is a bug in the last patch
[
https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521900
]
Erik Hatcher commented on SOLR-139:
---
One thing to note about overwrite and copyFields is that to keep a purely
[
https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521906
]
Erik Hatcher commented on SOLR-139:
---
I agree in the gut feel to how copyFields and overwrite should work, but what
[
https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521928
]
Erik Hatcher commented on SOLR-139:
---
A mistake I had was my copyField target (tag) was stored. Setting
[
https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520554
]
Erik Hatcher commented on SOLR-139:
---
I'm experimenting with this patch with tagging. I'm modeling the fields
I have a need for updateable documents and starting to tinker with
SOLR-139, but having issues with the latest patches applying:
$ curl https://issues.apache.org/jira/secure/attachment/12362787/
getStoredFields.patch | patch -p0 --dry-run
% Total% Received % Xferd Average Speed Time
that was quick! thanks ryan!
On Aug 14, 2007, at 2:15 PM, Ryan McKinley (JIRA) wrote:
[ https://issues.apache.org/jira/browse/SOLR-139?
page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan McKinley updated SOLR-139:
---
[
https://issues.apache.org/jira/browse/SOLR-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher resolved SOLR-329.
---
Resolution: Invalid
Solr most definitely recreates the data directory if it is not there during
[
https://issues.apache.org/jira/browse/SOLR-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher resolved SOLR-323.
---
Resolution: Fixed
duplicate lucene-analyzer jar files
[
https://issues.apache.org/jira/browse/SOLR-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513508
]
Erik Hatcher commented on SOLR-308:
---
Can the client get the generated id back when adding a document?
Add a field
On Jul 13, 2007, at 10:31 AM, Eric Pugh wrote:
I wanted to see if I could get some momentum going on seeing if
this is something that the committers want in Solr 1.3... I'd
like to write up a wiki page similar to http://wiki.apache.org/solr/
UpdateCSV page that would give folks a chance
[
https://issues.apache.org/jira/browse/SOLR-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher closed SOLR-163.
-
Resolution: Fixed
libxml/rexml-related test case failure
Begin forwarded message:
From: J Aaron Farr [EMAIL PROTECTED]
Call for Papers Opens for OS Summit Asia 2007
The call for papers is now open for OS Summit Asia, to be held
November 26-30 at the Cyberport in Hong Kong. This joint conference
between the Apache Software Foundation and the
On Jun 12, 2007, at 1:34 AM, Ryan McKinley wrote:
- !--
- dataDir./solr/data/dataDir
- --
+ dataDir${solr.data.dir:./solr/data}/dataDir
+
I just ran into something weird with this...
If you set the solr home with JNDI or solr.solr.home, the dataDir
still defaults to ./solr/data -- not
On Jun 12, 2007, at 12:37 PM, Ryan McKinley wrote:
Erik Hatcher wrote:
On Jun 12, 2007, at 1:34 AM, Ryan McKinley wrote:
- !--
- dataDir./solr/data/dataDir
- --
+ dataDir${solr.data.dir:./solr/data}/dataDir
+
I just ran into something weird with this...
If you set the solr home
+1
On Jun 2, 2007, at 6:19 PM, Yonik Seeley wrote:
OK, this one is it!
Please vote to release the artifacts at
http://people.apache.org/~yonik/staging_area/solr/1.2rc4/
as Apache Solr 1.2
+1
-Yonik
+1 again! :)
On May 31, 2007, at 7:02 PM, Yonik Seeley wrote:
Sorry folks... one more time. This release candidate fixes SOLR-250
(scripts need to tell curl the content-type), as well as the minor
README typo.
Please vote to release the artifacts at
[
https://issues.apache.org/jira/browse/SOLR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500083
]
Erik Hatcher commented on SOLR-84:
--
Those are great Steve! Thanks for submitting them.
New Solr logo
On May 29, 2007, at 4:38 PM, Mike Klaas wrote:
I agree. I was not aware of field boosts at the time. I'll code
this change.
Unfortunately, it is still somewhat awkward. In my python client I
end up passing (name, value, field boost or None) everywhere,
but that clutters up the api
+1
On May 30, 2007, at 9:23 PM, Yonik Seeley wrote:
Following a bug found and fixed by Ryan, I rebuilt the
release artifacts from branch-1.2 and placed them
at http://people.apache.org/~yonik/staging_area/solr/1.2rc2/
Please vote to release these artifacts as Apache Solr 1.2
Here's my +1
+1, thanks Yonik!
Yeah, the clients directory is still a work in progress. Eventually
Flare will be worth distributing with a release, but even then most
folks would want it to be installed from a plugin repository (or svn
directly). Same with the solr-ruby code, which is already
[
https://issues.apache.org/jira/browse/SOLR-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498767
]
Erik Hatcher commented on SOLR-246:
---
Yes, that resolves the issue very nicely!
INFO: /admin/luke numTerms=0wt
On May 22, 2007, at 10:42 PM, Ryan McKinley wrote:
If thats the case, I think the .diff you posted is fine...
Not really, because I commented out a bit to get past things. It was
more than just setting the default to zero.
The only thing I would change is I think the default should be
[
https://issues.apache.org/jira/browse/SOLR-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498311
]
Erik Hatcher commented on SOLR-247:
---
I can see value in supporting the dynamicField wildcard syntax, so *_facet
On May 21, 2007, at 11:00 PM, Ryan McKinley wrote:
If Ryan is date-less again tonight, I'm sure he'll have it all
fixed up by the time I wake up :) Otherwise, I'll dig in and roll
up my sleeves sometime this week and make some adjustments to
allow turning off the top terms feature.
Just
Ryan - just so you know where my current need with this is, it's only
in getting field names and types, as well as total documents back.
The top terms aren't a need for my projects. So I don't really have
any preference on the specifics, other than needing to be able to
turn that feature
[
https://issues.apache.org/jira/browse/SOLR-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher reassigned SOLR-241:
-
Assignee: Erik Hatcher
explicitly loggin an error message for missing system property for string
[
https://issues.apache.org/jira/browse/SOLR-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on SOLR-241 started by Erik Hatcher.
explicitly loggin an error message for missing system property for string
substitution in solrconfig.xml
[
https://issues.apache.org/jira/browse/SOLR-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher resolved SOLR-241.
---
Resolution: Fixed
Fix Version/s: 1.2
Thanks Koji!
explicitly loggin an error message
I've switched Flare to use the Luke request handler simply to
retrieve the fields in the index.
In the case of a 3.7M document index, it takes a LONG time to execute
because of the top terms its generating. I tried setting numTerms=0
and got an array index out of bounds exception. Is
Speaking of which, I'll be at RailsConf later this week and
presenting Solr on Rails there (covering solr-ruby, acts_as_solr,
and Solr Flare).
Erik
On May 13, 2007, at 9:17 PM, Ryan McKinley wrote:
Hello-
I'll be out of town for the next week... If i don't speak up, its
not
Besides the other replies on this thread, there is another really
nice way to tie a database dynamically to Solr. Use acts_as_solr.
The prerequisites are that you be using Ruby and ActiveRecord to
model your database tables. But its as easy as this:
class Book
[
https://issues.apache.org/jira/browse/SOLR-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher resolved SOLR-210.
---
Resolution: Fixed
Committed, thanks Jamie!
Next up: how to get solr-ruby to work without Hpricot
oops, thanks Ryan! I ran the tests before my change to make sure
all was well, and ran the solr-ruby tests (which rely on their own
config files afterwards.
Erik
On May 9, 2007, at 10:17 PM, [EMAIL PROTECTED] wrote:
Author: ryan
Date: Wed May 9 19:17:10 2007
New Revision:
On May 7, 2007, at 11:45 AM, Ryan McKinley (JIRA) wrote:
Ryan McKinley commented on SOLR-85:
---
This patch and SOLR-142 need to figure out how to deal with
arbitrary path mapping. Since the update command is not fixed to /
update and we also want to support
On May 6, 2007, at 2:13 AM, Ryan McKinley wrote:
As for the do we want it questions, i'm not really familiar with
easymock or jMock, so i don't have an opinion ...
I think we need something... without some mock framework, testing
HttpServlets is difficult.
+1
Testing through Java
This works fine on an older (trunk at some point a month or two ago)
version of Solr (in Ruby code):
Net::HTTP.new('localhost',).post(/solr/select,
wt=rubyq=rossetti, { Content-Type = application/x-www-form-
urlencoded; charset=utf-8 }).body
But on trunk I get an error that the q
On May 5, 2007, at 6:14 AM, Erik Hatcher wrote:
This works fine on an older (trunk at some point a month or two
ago) version of Solr (in Ruby code):
Net::HTTP.new('localhost',).post(/solr/select,
wt=rubyq=rossetti, { Content-Type = application/x-www-form-
urlencoded; charset=utf-8
On May 5, 2007, at 12:36 PM, Ryan McKinley wrote:
Erik Hatcher wrote:
On May 5, 2007, at 6:14 AM, Erik Hatcher wrote:
This works fine on an older (trunk at some point a month or two
ago) version of Solr (in Ruby code):
Net::HTTP.new('localhost',).post(/solr/select,
wt=rubyq
On May 2, 2007, at 7:10 PM, Ryan McKinley wrote:
and want:
copyField source=tag_(.*) dest=text_\1 /
Why even bother with regexs at all?
copyField source=tag_* dest=text_* /
simply replace the * match in the source in the * position in the
dest. Granted it doesn't have the power
[
https://issues.apache.org/jira/browse/SOLR-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher reassigned SOLR-210:
-
Assignee: Erik Hatcher
Hpricot Mapper for Solr-Ruby
[
https://issues.apache.org/jira/browse/SOLR-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492332
]
Erik Hatcher commented on SOLR-217:
---
I like Yonik's suggestion of allowing unstored+unindexed fields to be no-op
Sorry to be late to this game, but I already submitted two talks, one
a longer tutorial on Flare, and one a regular session on Flare. I'd
be happy to pair up with Eric Pugh as long as I get airfare and
hotel covered I'm happy to go.
Erik
On Apr 23, 2007, at 2:41 PM, Yonik
[
https://issues.apache.org/jira/browse/SOLR-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489395
]
Erik Hatcher commented on SOLR-209:
---
Rida - I'm curious about your approach why not normalize the (obviously
[
https://issues.apache.org/jira/browse/SOLR-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489092
]
Erik Hatcher commented on SOLR-193:
---
The latest patch has a typo:
public Document bulid
should be build
The one valid use of cross-posting...
Begin forwarded message:
From: Rich Bowen [EMAIL PROTECTED]
Date: April 16, 2007 10:50:54 AM EDT
To: [EMAIL PROTECTED]
Subject: Call for Papers Opens for ApacheCon US 2007
Reply-To: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
PMCs, please send this
Ryan et al - I've been experimenting with Solr running embedded as
shown in the wiki post below. I know there are better ways to do
some of these things and I'd love feedback on where this can use
improvement. For example, creating a document is a little clunky
with DocumentBuilder, but
: update
Reporter: Erik Hatcher
Priority: Trivial
It would be nice if the response from a delete by query returned the number
of documents deleted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/SOLR-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher resolved SOLR-184.
---
Resolution: Fixed
committed, and added unit test too.
add echoHandler=true to responseHeader
[
https://issues.apache.org/jira/browse/SOLR-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher reassigned SOLR-184:
-
Assignee: Erik Hatcher
add echoHandler=true to responseHeader, support echoParams=all
And likewise for my work with Solr as well.
Erik
On Apr 2, 2007, at 11:03 AM, Yonik Seeley wrote:
On 4/2/07, Maximilian Hütter [EMAIL PROTECTED] wrote:
I believe that Solr is never run
completely independent of other applications, as it would be rather
pointless to have a search
For those of you that feel very strongly about swapping out logging
frameworks, give AOP (such as AspectJ) a try to hook the logging. I
suspect it'd be possible to write a few AOP rules that would swap it
out nicely.
Erik
On Apr 2, 2007, at 5:43 PM, Chris Hostetter wrote:
:
On Mar 31, 2007, at 11:48 AM, Yonik Seeley wrote:
On 3/31/07, Erik Hatcher [EMAIL PROTECTED] wrote:
On a tab-delimited file I just got from a client, I got this error:
SEVERE: java.io.IOException: (line 119986) invalid char between
encapsualted token end delimiter
On Mar 30, 2007, at 4:49 AM, Maximilian Hütter wrote:
The added dependency is just one jar (apache project too), which is
not
a to high price to pay for the benefits pointed out before.
I can say with first hand experience that Commons Logging has caused
more pain than it was worth in
No objections at all.
I'm curious to see how you configured your IDE to run Solr tests, if
you can share the config.
Erik
On Mar 29, 2007, at 5:30 PM, Yonik Seeley wrote:
Anyone have an objection if the test that references these
is moved to use a different solrconfig.xml file?
I'm -1 on Commons Logging based on many JARmegaddon experiences with
other libraries that used it and getting all the dependencies
straightened out.
JDK logging suits me fine in Solr.
Erik
On Mar 29, 2007, at 6:59 PM, Chris Hostetter wrote:
: yes it would be nice if there
On Mar 16, 2007, at 3:28 PM, [EMAIL PROTECTED] wrote:
Author: otis
lucene/solr/trunk/example/exampledocs/spellchecher.xml
that should be spellchecker, not spellchecher.
On Mar 16, 2007, at 3:28 PM, [EMAIL PROTECTED] wrote:
+ str name=spellcheckerIndexDir/home/otis/dev/repos/lucene/
solr/trunk/example/solr/data/index/str
And this needs to be changed to something globally relevant. What
triggers the creation of this index? With this part of the
bad query messes up flare
-
Key: SOLR-189
URL: https://issues.apache.org/jira/browse/SOLR-189
Project: Solr
Issue Type: Bug
Components: clients - ruby - flare
Reporter: Erik Hatcher
[
https://issues.apache.org/jira/browse/SOLR-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher resolved SOLR-171.
---
Resolution: Fixed
Assignee: Erik Hatcher
Applied, thanks again Coda!
Add per-doc and per-field
On Feb 24, 2007, at 11:43 AM, Gmail Account wrote:
I guess I was more interested in the tagging part more than
anything. I was thinking that Collex was using tagging from Flare
and I wanted to see how it was being done or use it. I'm about to
try implementing tagging with my non-Ruby
I have a hard envisioning a case where a document would be indexed
without a unique identifier. While it *can* be done with just
Lucene, I've never seen a case where a unique key wasn't just a great
idea but a real necessity.
Erik
On Feb 24, 2007, at 6:10 PM, Ryan McKinley
On Feb 25, 2007, at 1:19 AM, Erik Hatcher wrote:
I have a hard envisioning a case where a document would be indexed
without a unique identifier. While it
^ time
*can* be done with just Lucene, I've never seen a case where a
unique key wasn't just a great idea but a real
On Feb 22, 2007, at 1:54 AM, Chris Hostetter wrote:
: I believe now having SolrQueryParser set the operator based on the
: schema configuration is much more sensible.
I haven't looked at this in depth, but i *think* this breaks the
DisMaxQueryParser (i'm guessing AND isn't the default in our
On Feb 22, 2007, at 1:58 PM, Chris Hostetter wrote:
: Does DisjunctionMaxQueryParser require the operator to be AND?
Does
: it always need to be set one way or the other? If so, we could just
: override that setting in the constructor, eh?
DisjunctionMaxQueryParser assumes that calling
On Feb 22, 2007, at 4:50 PM, Chris Hostetter wrote:
i agree overplaning is bad ... i just want to ensure any current
users of
new SolrQueryParser aren't suprised to find the behavior changing
out
from under them -- any future changes for more pluggable query parsers
will probably affect
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474012
]
Erik Hatcher commented on SOLR-20:
--
I want this on trunk also. I'll be reviewing it and testing it out
[
https://issues.apache.org/jira/browse/SOLR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher resolved SOLR-86.
--
Resolution: Fixed
Assignee: Erik Hatcher (was: Hoss Man)
Apologies to Hoss since this was assigned
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474032
]
Erik Hatcher commented on SOLR-20:
--
My bad... it was SOLR-86 that interested me, and I've just committed it.I
On Feb 18, 2007, at 8:19 PM, Chris Hostetter wrote:
: Log:
: Check in binary post.jar to make life easier for curl unfriendly
environments
:
: Added:
: lucene/solr/trunk/example/exampledocs/post.jar (with props)
whoa ... do we really want to commit the post.jar? .. it's built as
[
https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473920
]
Erik Hatcher commented on SOLR-162:
---
Ryan - I would like to see the Maps used instead of NamedLists for things
[
https://issues.apache.org/jira/browse/SOLR-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on SOLR-79 started by Erik Hatcher.
[PATCH] Using system properties in Solr configuration
-
Key
[
https://issues.apache.org/jira/browse/SOLR-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher resolved SOLR-79.
--
Resolution: Fixed
This feature has been added, complete with the requested exception handling
when
On Feb 16, 2007, at 3:26 PM, Otis Gospodnetic wrote:
I'm still torturing SOLR-81 - the spellchecker fronted with a Solr
RequestHandler.
Being a RequestHandler virgin, I'm not sure how to go from getting
the alternative
spelling suggestion(s) in the RequestHandler, to the output that
On Feb 16, 2007, at 4:28 PM, Ryan McKinley wrote:
On 2/16/07, Erik Hatcher [EMAIL PROTECTED] wrote:
from SolrDispatchFilter, we have this:
QueryResponseWriter responseWriter =
core.getQueryResponseWriter(solrReq);
response.setContentType(responseWriter.getContentType
Wow indeed! Go Ryan.
On Feb 16, 2007, at 6:07 PM, Yonik Seeley (JIRA) wrote:
[ https://issues.apache.org/jira/browse/SOLR-162?
page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanel#action_12473849 ]
Yonik Seeley commented on SOLR-162:
[
https://issues.apache.org/jira/browse/SOLR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473865
]
Erik Hatcher commented on SOLR-162:
---
This is truly great stuff, Ryan! *whew* I can't keep up.
I did however become
Mel,
I think I might have fixed the test_bad_connection issue you
encountered. Errno exceptions are platform specific and I simply
loosed the test to look for ::Exception (Solr::Exception gets in the
way, requiring :: prefix, I believe).
As for test_ping - I dunno. If you cd solr; java
401 - 500 of 615 matches
Mail list logo
