[
https://issues.apache.org/jira/browse/LUCENE-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277041#comment-13277041
]
Marvin Humphrey commented on LUCENE-4050:
-
Ever considered using hard l
must reside
within archived channels controlled by the ASF poses challenges when
attempting to integrate with a self-contained external hosting platform such
as Github. As that long thread on infrastructure-dev illustrates, though,
there is significant effort being expended to try to help
is not a spec. If it was, you'd have to fix
the implementation of Lucene to conform to the spec every time there was a
discrepancy.
Marvin Humphrey
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional co
[
https://issues.apache.org/jira/browse/LUCENE-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087704#comment-13087704
]
Marvin Humphrey commented on LUCENE-3218:
-
I don't fully grok Robert&
il client rather than use it as a list of JIRA URLs to go
visit.
Marvin Humphrey
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
On Tue, May 17, 2011 at 03:09:31PM -0400, Michael McCandless wrote:
> Yeah I agree... build failures should be as annoying as possible ;)
Congratulations -- mission accomplished! They are certainly annoying to me,
and probably to anyone else subscribed to dev who isn't a committer.
e designed a heuristic that allows you to filter a certain kind of
noise. It sounds a lot like how people tune length normalization to adapt to
their document collections. Many tuning techniques are corpus-specific.
Whatever works, works!
Marvin Humphrey
--
On Thu, Mar 31, 2011 at 11:45:53AM -0400, Grant Ingersoll wrote:
> Why do we need to publish PDFs again?
IIRC, publishing PDFs is the default in Forrest. It might have been a passive
choice.
Marvin Humphrey
-
To unsubscr
the time.
http://lucene.markmail.org/thread/jxshhiqr6wvq77xu
At least, that's the Matcher proposal I remember. :)
We ultimately did replace Scorer with Matcher in Lucy. Other pieces of that
proposal have found their way in
[
https://issues.apache.org/jira/browse/LUCENE-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982152#action_12982152
]
Marvin Humphrey commented on LUCENE-2858:
-
> Deleting docs from IR has adv
or Analyzer mismatches in a multi-node setup where e.g. the machine
that parses the query string and the machine which executes matching are not
the same.
Marvin Humphrey
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
g similar problems; then
one of the infra people freed up some disk space and the problem went away.
Marvin Humphrey
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[
https://issues.apache.org/jira/browse/LUCENE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marvin Humphrey closed LUCENE-851.
--
Resolution: Duplicate
Yes, LUCENE-2482 introduces the index sorter from Nutch that I referred
sible to turn off JIRA editing.
Marvin Humphrey
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[
https://issues.apache.org/jira/browse/LUCENE-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910668#action_12910668
]
Marvin Humphrey commented on LUCENE-2649:
-
> So: Please don't ad
ible.
Again, this in no way diminishes the value of Manning's potential contribution
or our gratitude for it. I just hope Manning understands why accommodating
their request perhaps isn't as easy as it might have seemed from the outside.
Marvin Humphrey
-
NGES.txt and what isn't. Rather than giving
credit, the primary purpose of the CHANGES file is to provide users
information they need to know when upgrading, isn't it?
However, I don't want to be too much of a stickler and get in the way of a
nice contribution here and now.
Th
every other contributor?
IMO, crediting in source code should be strictly limited to copyright and
licensing concerns; for everything else, credit belongs in version control and
the issue tracker.
Cheers,
Marvin Humphrey
--
[
https://issues.apache.org/jira/browse/LUCENE-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907506#action_12907506
]
Marvin Humphrey commented on LUCENE-2563:
-
The Lucy incubator website has bee
[
https://issues.apache.org/jira/browse/LUCENE-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901886#action_12901886
]
Marvin Humphrey commented on LUCENE-2617:
-
> Anyone know if null is actual
[
https://issues.apache.org/jira/browse/LUCENE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901057#action_12901057
]
Marvin Humphrey commented on LUCENE-675:
During the course of a recent IP audi
[
https://issues.apache.org/jira/browse/LUCENE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marvin Humphrey updated LUCENE-675:
---
Attachment: (was: LuceneIndexer.java)
> Lucene benchmark: objective performance test
[
https://issues.apache.org/jira/browse/LUCENE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marvin Humphrey updated LUCENE-675:
---
Attachment: (was: BenchmarkingIndexer.pm)
> Lucene benchmark: objective performance t
t, I don't think we can import a snapshot into Apache's
repository. So it's a bit of a catch-22.
Anybody have pointers to mailing list archives where complex provenance
efforts like this one were undertaken?
Marvin Humphrey
AdminGroup" group and then for us to edit that group?
http://wiki.apache.org/lucy/HelpOnAccessControlLists#Groups
Oo, I think this is a good idea:
https://issues.apache.org/jira/browse/INFRA-1029
We'd prefer change emails to go to ivy-comm...@incubator
Send change emails to the commits list rather than the dev list.
Marvin Humphrey
site in the short term, but IMO it's
better to proceed at leisure rather than worry about the site all-at-once
up-front. By going with what we have, we'll immediately look spiffier than a
lot of other incubating projects. :\
Marvin Humphrey
Check project name issues
-
Key: LUCY-121
URL: https://issues.apache.org/jira/browse/LUCY-121
Project: Lucy
Issue Type: Task
Components: Other
Reporter: Marvin Humphrey
Assignee
want to set up spam filtering. Having at least three
moderators is recommended to spread the load.
Volunteers? It hasn't been a heavy burden.
Marvin Humphrey
ing that you want to see a KinoSearch3 release?
>From my perspective, the sooner that KinoSearch gets EOL'd and we can focus on
Lucy development in earnest, the better. I wouldn't mind having some extra
pressure to release Lucy1 ASAP because we didn't release KinoSearch3. :)
Marvin Humphrey
.
o Add marvin and simonw.
o Get new accounts set up for Peter and Nate (CLAs are on file).
Marvin Humphrey
ent to the mailing lists as the move proceeds.
Marvin Humphrey
one minor content change, so I think we have adequate
consensus. I'm going to perform a QA pass and maybe tweak some phrasings so
that the word "community" doesn't appear eleventy-billion times. Then I'll
send it off to gene...@lucene.
Thanks, folks -- this has worked out well!
Marvin Humphrey
On Wed, Jun 30, 2010 at 05:01:45PM -0700, Marvin Humphrey wrote:
> On Wed, Jun 30, 2010 at 11:47:42PM -, Apache Wiki wrote:
> > + * Nathan Kurz has participated in numerous open source projects and has
> > been a KinoSearch committer since 2007. He is currently Chief Flavor
Nate, I didn't know what to write to describe your crazy bio, and I don't
think this does enough to convey your serious C and comp-sci chops.
I also don't think "Chief Flavor Engineer" is your title at Scream, though IMO
it ought to be.
Can you please edit?
Marvin Humphrey
.
So now, we propose to address that problem by supplying a code base. And I am
confident that with a code base in place, we will be able to focus effectively
on community building and develop into the kind of successful meritocracy that
Apache wants to foster.
Marvin Humphrey
s active, but all
the code that has ever gone into the existing Lucy repository was written
by the KinoSearch community.
Marvin Humphrey
ler, and we need to
flesh out Similarity.
Marvin Humphrey
[
https://issues.apache.org/jira/browse/LUCY-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marvin Humphrey resolved LUCY-118.
--
Resolution: Fixed
Committed as r95.
> Lucy::Index::DataReader - Abstract base class
[
https://issues.apache.org/jira/browse/LUCY-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marvin Humphrey resolved LUCY-119.
--
Resolution: Fixed
Committed as r957776.
> Lucy::Store::L
Feature
Components: Core - Index
Reporter: Marvin Humphrey
Assignee: Marvin Humphrey
Priority: Blocker
DataReader is an integral part of our modular index system, serving as a base
class for all component classes which read from the index - including both
[
https://issues.apache.org/jira/browse/LUCY-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marvin Humphrey resolved LUCY-117.
--
Resolution: Fixed
Committed as r956783, r956784, and r956785.
> More boolean Match
[
https://issues.apache.org/jira/browse/LUCY-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marvin Humphrey updated LUCY-112:
-
Attachment: polymatcher.patch
> PolyMatcher
> ---
>
> K
[
https://issues.apache.org/jira/browse/LUCY-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marvin Humphrey updated LUCY-111:
-
Attachment: Matcher.pm
> Matcher
> ---
>
> Key: LUCY-111
>
[
https://issues.apache.org/jira/browse/LUCY-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marvin Humphrey updated LUCY-111:
-
Attachment: Matcher.bp
Matcher.c
> Matcher
> ---
>
>
Matcher
---
Key: LUCY-111
URL: https://issues.apache.org/jira/browse/LUCY-111
Project: Lucy
Issue Type: New Feature
Components: Core - Search
Reporter: Marvin Humphrey
Assignee: Marvin Humphrey
[
https://issues.apache.org/jira/browse/LUCY-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marvin Humphrey resolved LUCY-108.
--
Resolution: Fixed
Committed as r953509.
> Numeric FieldTy
[
https://issues.apache.org/jira/browse/LUCY-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marvin Humphrey resolved LUCY-107.
--
Resolution: Fixed
Committed as r953507.
> BlobType
>
>
> K
[
https://issues.apache.org/jira/browse/LUCY-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marvin Humphrey resolved LUCY-106.
--
Resolution: Fixed
Committed as r953505.
> TextType
>
>
> K
#x27;t looked closely at Sphinx. That seems more like a userland
issue, unless you're proposing bringing in Sphinx as a Lucene subproject. ;)
Marvin Humphrey
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
Fo
[
https://issues.apache.org/jira/browse/LUCENE-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866693#action_12866693
]
Marvin Humphrey commented on LUCENE-2458:
-
> I'm honestly having
[
https://issues.apache.org/jira/browse/LUCENE-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866603#action_12866603
]
Marvin Humphrey commented on LUCENE-2458:
-
> Because they show its 10x be
[
https://issues.apache.org/jira/browse/LUCENE-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866595#action_12866595
]
Marvin Humphrey commented on LUCENE-2458:
-
I have mixed feelings about this
[
https://issues.apache.org/jira/browse/LUCENE-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865857#action_12865857
]
Marvin Humphrey commented on LUCENE-2167:
-
I find that it works well to p
h named "3x" rather than multiple branches
named e.g. "31", "32"... then here's my non-binding +1.
Marvin Humphrey
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
On Mon, May 03, 2010 at 06:21:08PM -0400, Erik Hatcher wrote:
> Can we please not use the word "stable"/"unstable" for these things?
One possibility: "maint_31", "maint_32", etc.
Marvin Humphrey
--
ing against the same index when those processes must be
allowed to create new deletions. I think there are insoluble race conditions
until you get into document-level locking.
I imagine NRT readers make this problem even harder.
Marvin Humphrey
-
56 matches
Mail list logo
