Re: [Lucene-java Wiki] Update of "PoweredBy" by ChristianShirts

I think so. Check the change before the one you linked: http://wiki.apache.org/jakarta-lucene/PoweredBy?action=diff&rev1=417&rev2=418 The link [[http://www.all-christian-t-shirts.com|Christian t-shirts]] is certainly not wanted. and now it looks like the "ChristianShirts" user is just making

Re: Hiding JIRA issues

See my other email for what I think the problem is and what to do about it. ( http://jira.atlassian.com/browse/JRA-15548 ) > JIRA allows for administrative export of the database to XML. If these don't export then something is really bad. The DB holds the correct information, but Lucene is st

Re: Hiding JIRA issues

e lock in the Lucene IssueIndexManager (in milliseconds) # This value should only be modified if you are seeing a jira.issue.index.DefaultIndexManager 'Giving up reindex' ERROR # in your log files or requested to do so by Atlassian support. jira.index.lock.waittime=3 HTH, Mark Lassau.

[jira] Commented: (LUCENE-1373) Most of the contributed Analyzers suffer from invalid recognition of acronyms.

[ https://issues.apache.org/jira/browse/LUCENE-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727390#action_12727390 ] Mark Lassau commented on LUCENE-1373: - @Rob This issue is about how Lucene pa

[jira] Commented: (LUCENE-1472) DateTools.stringToDate() can cause lock contention under load

[ https://issues.apache.org/jira/browse/LUCENE-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673771#action_12673771 ] Mark Lassau commented on LUCENE-1472: - An update for anyone interested: The test

[jira] Commented: (LUCENE-1472) DateTools.stringToDate() can cause lock contention under load

[ https://issues.apache.org/jira/browse/LUCENE-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652206#action_12652206 ] Mark Lassau commented on LUCENE-1472: - My original thought was ThreadLocal, b

[jira] Updated: (LUCENE-1472) DateTools.stringToDate() can cause lock contention under load

[ https://issues.apache.org/jira/browse/LUCENE-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Lassau updated LUCENE-1472: Description: Load testing our application (the JIRA Issue Tracker) has shown that threads spend

[jira] Commented: (LUCENE-1472) DateTools.stringToDate() can cause lock contention under load

[ https://issues.apache.org/jira/browse/LUCENE-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651900#action_12651900 ] Mark Lassau commented on LUCENE-1472: - [SimpleDateFormat javadoc|http://java.sun

[jira] Commented: (LUCENE-1472) DateTools.stringToDate() can cause lock contention under load

[ https://issues.apache.org/jira/browse/LUCENE-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651899#action_12651899 ] Mark Lassau commented on LUCENE-1472: - The following methods would potentially su

[jira] Created: (LUCENE-1472) DateTools.stringToDate() can cause lock contention under load

: Improvement Components: Search Affects Versions: 2.3.2 Reporter: Mark Lassau Priority: Minor Load testing our application (the JIRA Issue Tracker) has shown that threads spend a lot of time blocked in DateTools.stringToDate(). The stringToDate() method uses a

[jira] Commented: (LUCENE-1151) Fix StandardAnalyzer to not mis-identify HOST as ACRONYM by default

[ https://issues.apache.org/jira/browse/LUCENE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628590#action_12628590 ] Mark Lassau commented on LUCENE-1151: - Added a patch to LUCENE-1373 which moves

[jira] Updated: (LUCENE-1373) Most of the contributed Analyzers suffer from invalid recognition of acronyms.

[ https://issues.apache.org/jira/browse/LUCENE-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Lassau updated LUCENE-1373: Attachment: LUCENE-1373.patch Added a draft patch to fix the default behaviour of

[jira] Commented: (LUCENE-1151) Fix StandardAnalyzer to not mis-identify HOST as ACRONYM by default

[ https://issues.apache.org/jira/browse/LUCENE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628573#action_12628573 ] Mark Lassau commented on LUCENE-1151: - I love the solution you have come up with,

[jira] Commented: (LUCENE-1151) Fix StandardAnalyzer to not mis-identify HOST as ACRONYM by default

[ https://issues.apache.org/jira/browse/LUCENE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628568#action_12628568 ] Mark Lassau commented on LUCENE-1151: - Michael, Great work. I am glad we are mo

[jira] Issue Comment Edited: (LUCENE-1373) Most of the contributed Analyzers suffer from invalid recognition of acronyms.

>Affects Versions: 2.3.2 >Reporter: Mark Lassau >Priority: Minor > > LUCENE-1068 describes a bug in StandardTokenizer whereby a string like > "www.apache.org." would be incorrectly tokenized as an acronym (note the dot > at the end). >

Re: [jira] Commented: (LUCENE-1373) Most of the contributed Analyzers suffer from invalid recognition of acronyms.

t: Lucene - Java Issue Type: Bug Components: Analysis, contrib/analyzers Affects Versions: 2.3.2 Reporter: Mark Lassau Priority: Minor LUCENE-1068 describes a bug in StandardTokenizer whereby a string like "www.apache.org." would be incorrectl

[jira] Commented: (LUCENE-1373) Most of the contributed Analyzers suffer from invalid recognition of acronyms.

[ https://issues.apache.org/jira/browse/LUCENE-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627903#action_12627903 ] Mark Lassau commented on LUCENE-1373: - Had a closer look at the code, inclu

[jira] Commented: (LUCENE-1068) Invalid behavior of StandardTokenizerImpl

[ https://issues.apache.org/jira/browse/LUCENE-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627876#action_12627876 ] Mark Lassau commented on LUCENE-1068: - Causes JIRA issue [JRA-15484|

[jira] Commented: (LUCENE-1373) Most of the contributed Analyzers suffer from invalid recognition of acronyms.

[ https://issues.apache.org/jira/browse/LUCENE-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627875#action_12627875 ] Mark Lassau commented on LUCENE-1373: - Causes JIRA issue [JRA-15484|

[jira] Commented: (LUCENE-1373) Most of the contributed Analyzers suffer from invalid recognition of acronyms.

[ https://issues.apache.org/jira/browse/LUCENE-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627873#action_12627873 ] Mark Lassau commented on LUCENE-1373: - I would be willing to contribute a patc

[jira] Updated: (LUCENE-1373) Most of the contributed Analyzers suffer from invalid recognition of acronyms.

[ https://issues.apache.org/jira/browse/LUCENE-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Lassau updated LUCENE-1373: Description: LUCENE-1068 describes a bug in StandardTokenizer whereby a string like

[jira] Created: (LUCENE-1373) Most of the contributed Analyzers suffer from invalid recognition of acronyms.

- Java Issue Type: Bug Components: Analysis, contrib/analyzers Affects Versions: 2.3.2 Reporter: Mark Lassau Priority: Minor LUCENE-1068 describes a bug in StandardTokenizer whereby a string like "www.apache.org." would be incorrectly token

[jira] Commented: (LUCENE-1175) occasional MergeException while indexing

[ https://issues.apache.org/jira/browse/LUCENE-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625641#action_12625641 ] Mark Lassau commented on LUCENE-1175: - >From reading this issue, it is