gust 19, 2008 3:06:27 PM
Subject: Solr 1.3 Status, Lucene Status was Re: [jira] Commented:
(SOLR-697) Update Lucene jar before 1.3 release
I'm not sure where I stand on waiting for Lucene 2.4. It's at
least a
month away in my mind anyway due to the number of issues on it and
Lucen
ht's build and the problem has been
resolved.
Thanks Yonik!
> Update Lucene jar before 1.3 release (was: Lucene TimeLimitCollector)
> -
>
> Key: SOLR-697
> URL: https://issues.apa
- Original Message
> From: Grant Ingersoll <[EMAIL PROTECTED]>
> To: solr-dev@lucene.apache.org
> Sent: Tuesday, August 19, 2008 3:06:27 PM
> Subject: Solr 1.3 Status, Lucene Status was Re: [jira] Commented: (SOLR-697)
> Update Lucene jar before 1.3 release
>
> I&#x
ixed please?
> Update Lucene jar before 1.3 release (was: Lucene TimeLimitCollector)
> -
>
> Key: SOLR-697
> URL: https://issues.apache.org/jira/browse/SOLR-697
> Project:
[
https://issues.apache.org/jira/browse/SOLR-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-697.
---
Resolution: Fixed
Resolving... I just updated the lucene jars.
> Update Lucene jar before 1.3 rele
fixfor=12312681
[2] Solr Issues
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310230&fixfor=12312486
On Aug 19, 2008, at 9:25 AM, Mark Miller wrote:
Now that Lucene 1.4 looks und
Now that Lucene 1.4 looks underway, there seems to be a bit of a
dilemma. Solr 1.3 release seems to be planned a bit ahead of Lucene 1.4.
Release just before a Lucene release, or wait and get a nice even Lucene
1.4 release?
Even if there is a wait for 1.4, if the past is any clue, solr 1.3
ater (i.e. now) so that people get a
chance to test everything before the 1.3 release?
> Update Lucene jar before 1.3 release (was: Lucene TimeLimitCollector)
> -
>
> Key: SOLR-697
>
I'm leaving for vacation tomorrow and will have little or no internet
access until sept 1 -- from the 1st to the 7th, I will have limited
access. The one remaining issue that I am concerned about for 1.3 is
how to set the "dataDir" for various cores in a multicore environment
-- SOLR-646 a
[
https://issues.apache.org/jira/browse/SOLR-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic reopened SOLR-697:
---
Ahaaa!
> Update Lucene jar before 1.3 release (was: Lucene TimeLimitCollec
[
https://issues.apache.org/jira/browse/SOLR-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic updated SOLR-697:
--
Summary: Update Lucene jar before 1.3 release (was: Lucene
TimeLimitCollector) (was: Lucene
I've committed my last *big* changes for 1.3 -- I hope the multicore
stuff is now more clear.
The only remaining issue I need to handle to make setting different
dataDirs for various cores easier. If SOLR-646 becomes simpler, this
may be done via manageable system properties. Otherwise we
On Wed, Jul 30, 2008 at 5:01 AM, Shalin Shekhar Mangar
<[EMAIL PROTECTED]> wrote:
> We can't release with Lucene trunk jars, can we?
We can if we feel comfortable with it.
-Yonik
There are more. SpellCheckComponent and support for partial optimizes also
depend on features in Lucene trunk.
On Wed, Jul 30, 2008 at 2:40 PM, Lars Kotthoff <[EMAIL PROTECTED]> wrote:
> > We can't release with Lucene trunk jars, can we?
>
> Ah, that reminds me of something. The feature added in
> We can't release with Lucene trunk jars, can we?
Ah, that reminds me of something. The feature added in SOLR-610 sort-of depends
on LUCENE-1321 to work properly. This will only bite people who use SOLR-610 and
try to highlight something at the very end of the field, so I don't think it's
much of
We can't release with Lucene trunk jars, can we?
On Mon, Jul 28, 2008 at 6:24 PM, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 10, 2008 at 11:56 AM, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> > So how about we make a 1.3 branch in about 2 weeks (the 25th), and
> > release soon after.
>
>
Let us do another round of bug scrubbing, Identify all the issues to
be fixed in this release and defer some if it is not important for
this release.
On Mon, Jul 28, 2008 at 6:24 PM, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 10, 2008 at 11:56 AM, Yonik Seeley <[EMAIL PROTECTED]> wrote:
On Thu, Jul 10, 2008 at 11:56 AM, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> So how about we make a 1.3 branch in about 2 weeks (the 25th), and
> release soon after.
Given the flurry of recent activity, seems like extending this a
little longer (another week?) would be a good idea.
-Yonik
On Sun, 13 Jul 2008 02:00:24 +1000
Norberto Meijome <[EMAIL PROTECTED]> wrote:
> On Thu, 10 Jul 2008 11:56:00 -0400
> "Yonik Seeley" <[EMAIL PROTECTED]> wrote:
>
> > I think we need to put a stake in the ground for the 1.3 release...
> > more issue
- Lucene - Solr - Nutch
- Original Message
From: Norberto Meijome <[EMAIL PROTECTED]>
To: solr-dev@lucene.apache.org
Sent: Saturday, July 12, 2008 6:40:44 PM
Subject: Re: Solr 1.3 release date
On Sat, 12 Jul 2008 12:25:32 -0400
"Yonik Seeley" wrote:
1) The current version
seen any
> problems with it.
>
>
> Otis
> --
> Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
>
>
>
> - Original Message
>> From: Norberto Meijome <[EMAIL PROTECTED]>
>> To: solr-dev@lucene.apache.org
>> Sent: Saturday, July
g
> Sent: Saturday, July 12, 2008 6:40:44 PM
> Subject: Re: Solr 1.3 release date
>
> On Sat, 12 Jul 2008 12:25:32 -0400
> "Yonik Seeley" wrote:
>
> > 1) The current version has been tested for a year with this specific
> > application (Solr) and thus
s a
comparison point... as I understand it, there have been some performance
improvements in Jetty, at least on/from 6.1.5, but I don't know enough about it
to say whether they would affect a SOLR installation.
> IMO, If we don't upgrade now, it makes sense to upgrade immediately
>
.
and just because we don't think we've encountered bugs in the old
version doesn't mean that others won't.
IMO, If we don't upgrade now, it makes sense to upgrade immediately
after a 1.3 release.
-Yonik
On Thu, 10 Jul 2008 11:56:00 -0400
"Yonik Seeley" <[EMAIL PROTECTED]> wrote:
> I think we need to put a stake in the ground for the 1.3 release...
> more issues have been added, and in this mode we will never get there.
>
> Some items *should* hold up a release:
>
I'd just put comments at the top of the classes in the javadocs, maybe
just at the main entry points.
-Grant
On Jul 12, 2008, at 12:43 AM, Noble Paul നോബിള്
नोब्ळ् wrote:
How to make it mark as experimental? in Jira?
On Sat, Jul 12, 2008 at 3:19 AM, Grant Ingersoll
<[EMAIL PROTECTED]>
How to make it mark as experimental? in Jira?
On Sat, Jul 12, 2008 at 3:19 AM, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
>
> On Jul 10, 2008, at 1:57 PM, Noble Paul നോബിള് नोब्ळ् wrote:
>
>> The contrib patch is already committed. So DIH must be going into
>> contrib. DIH will be an extra jar in
On Jul 10, 2008, at 1:57 PM, Noble Paul നോബിള്
नोब्ळ् wrote:
The contrib patch is already committed. So DIH must be going into
contrib. DIH will be an extra jar in the distro.
Yes, that is my plan.
If new features/fixes come up later the new jar can be dropped in and
nothing else must
> I'd prefer not rushing that in, as it is a big contribution and needs
> a bit more review. (personally I think Spring MVC is overkill and
> less flexible, more verbose, than alternatives, but I'm strongly
> opinionated and will defer to others that desire this UI in Solr's
> codebase).
On Jul 10, 2008, at 7:37 PM, Lars Kotthoff wrote:
How about getting the user interface I wrote in with the release? I
think it'd
make a nice addition as something that's directly visible to the end-
user.
I'd prefer not rushing that in, as it is a big contribution and needs
a bit more revi
How about getting the user interface I wrote in with the release? I think it'd
make a nice addition as something that's directly visible to the end-user.
Lars
The contrib patch is already committed. So DIH must be going into
contrib. DIH will be an extra jar in the distro.
If new features/fixes come up later the new jar can be dropped in and
nothing else must break.
If all the the external interfaces/(API & XML) are fine, any other
changes that might co
On Thu, Jul 10, 2008 at 12:40 PM, Chris Hostetter
<[EMAIL PROTECTED]> wrote:
> : We've had enough new features to warrant a new release for quite a
> : while, so I don't think any new big features should be going in unless
> : they are ready right now.
>
> Looking at the pending issues, the only bi
: We've had enough new features to warrant a new release for quite a
: while, so I don't think any new big features should be going in unless
: they are ready right now.
Looking at the pending issues, the only biggee seems to be SOLR-469,
DataImportHandler ... my impression from the list is tha
I think we need to put a stake in the ground for the 1.3 release...
more issues have been added, and in this mode we will never get there.
Some items *should* hold up a release:
- stability issues
- review of new APIs that will become finalized on release
We've had enough new features to wa
35 matches
Mail list logo
