https://issues.apache.org/jira/browse/SOLR-426
On Dec 5, 2007 9:57 AM, Ryan McKinley <[EMAIL PROTECTED]> wrote:
>
> Charles Hornberger wrote:
> > On Dec 4, 2007 6:25 PM, Chris Hostetter <[EMAIL PROTECTED]> wrote:
> >> i'm not sure what you mean by "applied to 1.2" ... releases are static:
> >> onc
Charles Hornberger wrote:
On Dec 4, 2007 6:25 PM, Chris Hostetter <[EMAIL PROTECTED]> wrote:
i'm not sure what you mean by "applied to 1.2" ... releases are static:
once published they are never changed. in the event of serious bugs (ie:
security holes or crash related bugs) then point releases
On Dec 4, 2007 6:25 PM, Chris Hostetter <[EMAIL PROTECTED]> wrote:
>
> i'm not sure what you mean by "applied to 1.2" ... releases are static:
> once published they are never changed. in the event of serious bugs (ie:
> security holes or crash related bugs) then point releases may be published
> (
: It's a trivial fix, and it seems like it's already been done in trunk:
:
:
http://svn.apache.org/viewvc/lucene/solr/trunk/src/scripts/commit?r1=543259&r2=555612&view=patch
:
: The change has not been applied to 1.2. It might be nice if it were.
i'm not sure what you mean by "applied to 1
LIke others before me, I stumbled across this bug, where
solr/bin/commit warns that a commit failed when in fact it succeeded
quite nicely, while getting collection distribution up & running
today:
http://www.mail-archive.com/solr-user@lucene.apache.org/msg04585.html
It's a trivial fix, and i
