[
https://issues.apache.org/jira/browse/LUCENE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641309#action_12641309
]
Michael McCandless commented on LUCENE-1422:
Michael I think you left out oal.
[
https://issues.apache.org/jira/browse/LUCENE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641322#action_12641322
]
Michael McCandless commented on LUCENE-1422:
bq. Would it be better to add the
[
https://issues.apache.org/jira/browse/LUCENE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch updated LUCENE-1422:
--
Attachment: lucene-1422.take3.patch
Oups, sorry, this should work now.
Another question: Is i
On Oct 21, 2008, at 1:39 AM, Michael Busch wrote:
Perhaps it would be useful for Lucene to offer exactly one subclass
of Token that we guarantee will always have all known Attributes
(i.e. the ones Lucene provides) available to it for casting
purposes.
Yeah we could do that. In fact,
[
https://issues.apache.org/jira/browse/LUCENE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641334#action_12641334
]
Michael McCandless commented on LUCENE-1422:
{quote}
Another question: Is it c
[
https://issues.apache.org/jira/browse/LUCENE-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved LUCENE-1406.
-
Resolution: Fixed
Fix Version/s: 2.9
Lucene Fields: [Patch Available] (was: [
On Oct 17, 2008, at 5:06 PM, Ryan McKinley wrote:
Todd Feak just added a few Filter implementations to solr JIRA:
https://issues.apache.org/jira/browse/SOLR-815
https://issues.apache.org/jira/browse/SOLR-814
https://issues.apache.org/jira/browse/SOLR-813
I don't know anything about Japanese, s
Grant Ingersoll wrote:
On Oct 21, 2008, at 1:39 AM, Michael Busch wrote:
Perhaps it would be useful for Lucene to offer exactly one subclass
of Token that we guarantee will always have all known Attributes
(i.e. the ones Lucene provides) available to it for casting purposes.
Yeah we cou
[
https://issues.apache.org/jira/browse/LUCENE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641530#action_12641530
]
Michael Busch commented on LUCENE-1422:
---
{quote}
I think it would be slightly better
[
https://issues.apache.org/jira/browse/LUCENE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641549#action_12641549
]
Michael McCandless commented on LUCENE-1422:
bq. I should probably add a start
[
https://issues.apache.org/jira/browse/LUCENE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641567#action_12641567
]
Michael Busch commented on LUCENE-1422:
---
{quote}
I think that's the right approach!
[
https://issues.apache.org/jira/browse/LUCENE-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641574#action_12641574
]
Michael Busch commented on LUCENE-1426:
---
{quote}
+1 This sounds like a great way to
[
https://issues.apache.org/jira/browse/LUCENE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641580#action_12641580
]
DM Smith commented on LUCENE-1422:
--
bq.Another question. Currently the members in Token,
[
https://issues.apache.org/jira/browse/LUCENE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641583#action_12641583
]
Michael Busch commented on LUCENE-1422:
---
{quote}
Strictly speaking, it does break ba
So, we got 2.4 out of the way (thanks, Mike!) and we have agreed,
pending build releases, that we are ready to move onto 2.9 and then
3.0. Our strategy for this is generally to mark in 2.9 all things
that we want to remove as deprecated, such that one needs to address
the deprecations in o
[
https://issues.apache.org/jira/browse/LUCENE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641598#action_12641598
]
Grant Ingersoll commented on LUCENE-1422:
-
{quote}
Yes I agree. But my take here i
[
https://issues.apache.org/jira/browse/LUCENE-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641599#action_12641599
]
Paul Elschot commented on LUCENE-1426:
--
bq. ... it would make sense to use VInts for
[
https://issues.apache.org/jira/browse/LUCENE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641600#action_12641600
]
Michael Busch commented on LUCENE-1422:
---
{quote}
Said vote could either be specific
Currently Lucene's backwards compatibility policy states: "That's to
say, any code developed against X.0 should continue to run without
alteration against all X.N releases." In LUCENE-1422 the question came
up if this statement should apply to public and protected APIs only or
also to package-p
Michael Busch wrote:
Currently Lucene's backwards compatibility policy states: "That's to
say, any code developed against X.0 should continue to run without
alteration against all X.N releases." In LUCENE-1422 the question came
up if this statement should apply to public and protected APIs only
Doug Cutting wrote:
Michael Busch wrote:
Currently Lucene's backwards compatibility policy states: "That's to
say, any code developed against X.0 should continue to run without
alteration against all X.N releases." In LUCENE-1422 the question
came up if this statement should apply to public an
: //BUT WHEN I GET TEXT LIKE THAT TO ADD TO THE INDEX
: textData = stripper.getText(document);
have you looked at the String in textData to make sure it's what you
expect?
: This code above properly saves extracted text to the txt file, whioch I dotn
: really need. What I want is to get text an
[
https://issues.apache.org/jira/browse/LUCENE-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641717#action_12641717
]
Alison Winters commented on LUCENE-1342:
We have hit this issue in our QA environm
23 matches
Mail list logo
