[jira] [Commented] (LUCENE-5339) Simplify the facet module APIs

[ https://issues.apache.org/jira/browse/LUCENE-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13857995#comment-13857995 ] Michael McCandless commented on LUCENE-5339: Thanks Shai. I'd rather not add

[jira] [Commented] (LUCENE-5376) Add a demo search server

[ https://issues.apache.org/jira/browse/LUCENE-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858014#comment-13858014 ] ASF subversion and git services commented on LUCENE-5376: - Commit

[jira] [Commented] (LUCENE-5378) Enable using extended field types with prefix queries for non-default encoded strings

[ https://issues.apache.org/jira/browse/LUCENE-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858072#comment-13858072 ] Anshum Gupta commented on LUCENE-5378: -- Thanks for the suggestion Yonik. Coming to

[jira] [Commented] (SOLR-5580) NPE when create a core with both explicite shard and coreNodeName

[ https://issues.apache.org/jira/browse/SOLR-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858090#comment-13858090 ] Bill Bell commented on SOLR-5580: - This looks good to me. I also like the log.info() NPE

[jira] [Commented] (SOLR-5577) indexing delay due to zookeeper election

[ https://issues.apache.org/jira/browse/SOLR-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858108#comment-13858108 ] ASF subversion and git services commented on SOLR-5577: --- Commit

[jira] [Commented] (SOLR-5577) indexing delay due to zookeeper election

[ https://issues.apache.org/jira/browse/SOLR-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858109#comment-13858109 ] ASF subversion and git services commented on SOLR-5577: --- Commit

RE: JDK 7 Update 60 build 02 is available on java.net

Hi Rory, I will install this update (and also latest Java 8 build) during the next days. Currently I am out for vacation. Uwe - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de/ http://www.thetaphi.de eMail: u...@thetaphi.de From: Rory O'Donnell

[JENKINS-MAVEN] Lucene-Solr-Maven-4.x #546: POMs out of sync

Build: https://builds.apache.org/job/Lucene-Solr-Maven-4.x/546/ 2 tests failed. REGRESSION: org.apache.solr.cloud.BasicDistributedZk2Test.testDistribSearch Error Message: No live SolrServers available to handle this request:[http://127.0.0.1:30923/collection1,

[jira] [Commented] (SOLR-5442) Python client cannot parse proxied response when served by Tomcat.

[ https://issues.apache.org/jira/browse/SOLR-5442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858137#comment-13858137 ] ASF subversion and git services commented on SOLR-5442: --- Commit

[jira] [Commented] (SOLR-5445) Proxied responses should propagate all headers rather than the first one for each key.

[ https://issues.apache.org/jira/browse/SOLR-5445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858138#comment-13858138 ] ASF subversion and git services commented on SOLR-5445: --- Commit

[jira] [Commented] (SOLR-5442) Python client cannot parse proxied response when served by Tomcat.

[ https://issues.apache.org/jira/browse/SOLR-5442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858140#comment-13858140 ] ASF subversion and git services commented on SOLR-5442: --- Commit

[jira] [Commented] (SOLR-5445) Proxied responses should propagate all headers rather than the first one for each key.

[ https://issues.apache.org/jira/browse/SOLR-5445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858141#comment-13858141 ] ASF subversion and git services commented on SOLR-5445: --- Commit

[jira] [Updated] (SOLR-5445) Proxied responses should propagate all headers rather than the first one for each key.

[ https://issues.apache.org/jira/browse/SOLR-5445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-5445: -- Fix Version/s: 4.6.1 4.7 5.0 Proxied responses should propagate

[jira] [Commented] (SOLR-5479) SolrCmdDistributor retry logic stops if a leader for the request cannot be found in 1 second.

[ https://issues.apache.org/jira/browse/SOLR-5479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858144#comment-13858144 ] ASF subversion and git services commented on SOLR-5479: --- Commit

[jira] [Commented] (SOLR-5442) Python client cannot parse proxied response when served by Tomcat.

[ https://issues.apache.org/jira/browse/SOLR-5442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858142#comment-13858142 ] ASF subversion and git services commented on SOLR-5442: --- Commit

[jira] [Commented] (SOLR-5479) SolrCmdDistributor retry logic stops if a leader for the request cannot be found in 1 second.

[ https://issues.apache.org/jira/browse/SOLR-5479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858146#comment-13858146 ] ASF subversion and git services commented on SOLR-5479: --- Commit

[jira] [Commented] (SOLR-5445) Proxied responses should propagate all headers rather than the first one for each key.

[ https://issues.apache.org/jira/browse/SOLR-5445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858143#comment-13858143 ] ASF subversion and git services commented on SOLR-5445: --- Commit

[jira] [Commented] (SOLR-5479) SolrCmdDistributor retry logic stops if a leader for the request cannot be found in 1 second.

[ https://issues.apache.org/jira/browse/SOLR-5479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858145#comment-13858145 ] ASF subversion and git services commented on SOLR-5479: --- Commit

[jira] [Updated] (SOLR-5479) SolrCmdDistributor retry logic stops if a leader for the request cannot be found in 1 second.

[ https://issues.apache.org/jira/browse/SOLR-5479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-5479: -- Fix Version/s: 4.6.1 SolrCmdDistributor retry logic stops if a leader for the request cannot be

[jira] [Commented] (SOLR-5479) SolrCmdDistributor retry logic stops if a leader for the request cannot be found in 1 second.

[ https://issues.apache.org/jira/browse/SOLR-5479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858147#comment-13858147 ] ASF subversion and git services commented on SOLR-5479: --- Commit

[jira] [Commented] (SOLR-5532) SolrJ Content-Type validation is too strict for some webcontainers / proxies, breaks on equivilent content types

[ https://issues.apache.org/jira/browse/SOLR-5532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858148#comment-13858148 ] ASF subversion and git services commented on SOLR-5532: --- Commit

[jira] [Updated] (SOLR-5532) SolrJ Content-Type validation is too strict for some webcontainers / proxies, breaks on equivilent content types

[ https://issues.apache.org/jira/browse/SOLR-5532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-5532: -- Fix Version/s: 4.6.1 SolrJ Content-Type validation is too strict for some webcontainers / proxies,

[jira] [Commented] (SOLR-5532) SolrJ Content-Type validation is too strict for some webcontainers / proxies, breaks on equivilent content types

[ https://issues.apache.org/jira/browse/SOLR-5532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858150#comment-13858150 ] ASF subversion and git services commented on SOLR-5532: --- Commit

[jira] [Commented] (SOLR-5532) SolrJ Content-Type validation is too strict for some webcontainers / proxies, breaks on equivilent content types

[ https://issues.apache.org/jira/browse/SOLR-5532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858149#comment-13858149 ] ASF subversion and git services commented on SOLR-5532: --- Commit

[jira] [Commented] (SOLR-5576) ZkController.java registerAllCoresAsDown multiple cores logic

[ https://issues.apache.org/jira/browse/SOLR-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858151#comment-13858151 ] ASF subversion and git services commented on SOLR-5576: --- Commit

[jira] [Commented] (SOLR-5576) ZkController.java registerAllCoresAsDown multiple cores logic

[ https://issues.apache.org/jira/browse/SOLR-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858153#comment-13858153 ] ASF subversion and git services commented on SOLR-5576: --- Commit

[jira] [Commented] (SOLR-5576) ZkController.java registerAllCoresAsDown multiple cores logic

[ https://issues.apache.org/jira/browse/SOLR-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858152#comment-13858152 ] ASF subversion and git services commented on SOLR-5576: --- Commit

[jira] [Updated] (SOLR-5580) NPE when create a core with both explicite shard and coreNodeName

[ https://issues.apache.org/jira/browse/SOLR-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-5580: -- Fix Version/s: 4.6.1 4.7 5.0 Assignee: Mark Miller NPE

[jira] [Commented] (SOLR-5580) NPE when create a core with both explicite shard and coreNodeName

[ https://issues.apache.org/jira/browse/SOLR-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858162#comment-13858162 ] Mark Miller commented on SOLR-5580: --- This was introduced by SOLR-5311. NPE when create

[jira] [Commented] (SOLR-5580) NPE when create a core with both explicite shard and coreNodeName

[ https://issues.apache.org/jira/browse/SOLR-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858163#comment-13858163 ] Mark Miller commented on SOLR-5580: --- That whole bit looks silly and dangerous to me. I'm

[jira] [Commented] (SOLR-5580) NPE when create a core with both explicite shard and coreNodeName

[ https://issues.apache.org/jira/browse/SOLR-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858164#comment-13858164 ] ASF subversion and git services commented on SOLR-5580: --- Commit

[jira] [Commented] (SOLR-5580) NPE when create a core with both explicite shard and coreNodeName

[ https://issues.apache.org/jira/browse/SOLR-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858166#comment-13858166 ] ASF subversion and git services commented on SOLR-5580: --- Commit

[jira] [Commented] (SOLR-5580) NPE when create a core with both explicite shard and coreNodeName

[ https://issues.apache.org/jira/browse/SOLR-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858165#comment-13858165 ] ASF subversion and git services commented on SOLR-5580: --- Commit

[jira] [Resolved] (SOLR-5580) NPE when create a core with both explicite shard and coreNodeName

[ https://issues.apache.org/jira/browse/SOLR-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller resolved SOLR-5580. --- Resolution: Fixed Thanks YouPeng! NPE when create a core with both explicite shard and

[jira] [Commented] (SOLR-5552) Leader recovery process can select the wrong leader if all replicas for a shard are down and trying to recover as well as lose updates that should have been recovered.

[ https://issues.apache.org/jira/browse/SOLR-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858168#comment-13858168 ] Mark Miller commented on SOLR-5552: --- Sweet, thanks! Leader recovery process can select

[jira] [Commented] (SOLR-5569) A replica should not try and recover from a leader until it has published that it is ACTIVE.

[ https://issues.apache.org/jira/browse/SOLR-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858170#comment-13858170 ] ASF subversion and git services commented on SOLR-5569: --- Commit

[jira] [Commented] (SOLR-5552) Leader recovery process can select the wrong leader if all replicas for a shard are down and trying to recover as well as lose updates that should have been recovered.

[ https://issues.apache.org/jira/browse/SOLR-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858169#comment-13858169 ] ASF subversion and git services commented on SOLR-5552: --- Commit

[jira] [Commented] (SOLR-5569) A replica should not try and recover from a leader until it has published that it is ACTIVE.

[ https://issues.apache.org/jira/browse/SOLR-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858173#comment-13858173 ] ASF subversion and git services commented on SOLR-5569: --- Commit

[jira] [Commented] (SOLR-5552) Leader recovery process can select the wrong leader if all replicas for a shard are down and trying to recover as well as lose updates that should have been recovered.

[ https://issues.apache.org/jira/browse/SOLR-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858172#comment-13858172 ] ASF subversion and git services commented on SOLR-5552: --- Commit

[jira] [Commented] (SOLR-5568) A SolrCore cannot decide to be the leader just because the cluster state says no other SolrCore's are active.

[ https://issues.apache.org/jira/browse/SOLR-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858171#comment-13858171 ] ASF subversion and git services commented on SOLR-5568: --- Commit

[jira] [Commented] (SOLR-5568) A SolrCore cannot decide to be the leader just because the cluster state says no other SolrCore's are active.

[ https://issues.apache.org/jira/browse/SOLR-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858174#comment-13858174 ] ASF subversion and git services commented on SOLR-5568: --- Commit

[jira] [Commented] (SOLR-5568) A SolrCore cannot decide to be the leader just because the cluster state says no other SolrCore's are active.

[ https://issues.apache.org/jira/browse/SOLR-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858179#comment-13858179 ] ASF subversion and git services commented on SOLR-5568: --- Commit

[jira] [Commented] (SOLR-5552) Leader recovery process can select the wrong leader if all replicas for a shard are down and trying to recover as well as lose updates that should have been recovered.

[ https://issues.apache.org/jira/browse/SOLR-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858177#comment-13858177 ] ASF subversion and git services commented on SOLR-5552: --- Commit

[jira] [Commented] (SOLR-5569) A replica should not try and recover from a leader until it has published that it is ACTIVE.

[ https://issues.apache.org/jira/browse/SOLR-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858178#comment-13858178 ] ASF subversion and git services commented on SOLR-5569: --- Commit

[jira] [Resolved] (SOLR-5568) A SolrCore cannot decide to be the leader just because the cluster state says no other SolrCore's are active.

[ https://issues.apache.org/jira/browse/SOLR-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller resolved SOLR-5568. --- Resolution: Fixed A SolrCore cannot decide to be the leader just because the cluster state says no

[jira] [Commented] (SOLR-5569) A replica should not try and recover from a leader until it has published that it is ACTIVE.

[ https://issues.apache.org/jira/browse/SOLR-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858180#comment-13858180 ] ASF subversion and git services commented on SOLR-5569: --- Commit

[jira] [Resolved] (SOLR-5569) A replica should not try and recover from a leader until it has published that it is ACTIVE.

[ https://issues.apache.org/jira/browse/SOLR-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller resolved SOLR-5569. --- Resolution: Fixed A replica should not try and recover from a leader until it has published that

[jira] [Commented] (SOLR-5547) SolrJ Create Alias Incorrect/Failing

[ https://issues.apache.org/jira/browse/SOLR-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858182#comment-13858182 ] ASF subversion and git services commented on SOLR-5547: --- Commit

[jira] [Commented] (SOLR-5552) Leader recovery process can select the wrong leader if all replicas for a shard are down and trying to recover as well as lose updates that should have been recovered.

[ https://issues.apache.org/jira/browse/SOLR-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858184#comment-13858184 ] ASF subversion and git services commented on SOLR-5552: --- Commit

[jira] [Commented] (SOLR-5569) A replica should not try and recover from a leader until it has published that it is ACTIVE.

[ https://issues.apache.org/jira/browse/SOLR-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858185#comment-13858185 ] ASF subversion and git services commented on SOLR-5569: --- Commit

[jira] [Commented] (SOLR-5568) A SolrCore cannot decide to be the leader just because the cluster state says no other SolrCore's are active.

[ https://issues.apache.org/jira/browse/SOLR-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858186#comment-13858186 ] ASF subversion and git services commented on SOLR-5568: --- Commit

[jira] [Commented] (SOLR-5547) SolrJ Create Alias Incorrect/Failing

[ https://issues.apache.org/jira/browse/SOLR-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858187#comment-13858187 ] ASF subversion and git services commented on SOLR-5547: --- Commit

[jira] [Commented] (SOLR-5547) SolrJ Create Alias Incorrect/Failing

[ https://issues.apache.org/jira/browse/SOLR-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858188#comment-13858188 ] ASF subversion and git services commented on SOLR-5547: --- Commit

[jira] [Updated] (SOLR-5547) SolrJ Create Alias Incorrect/Failing

[ https://issues.apache.org/jira/browse/SOLR-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-5547: -- Fix Version/s: 4.6.1 SolrJ Create Alias Incorrect/Failing

[jira] [Commented] (SOLR-5577) indexing delay due to zookeeper election

[ https://issues.apache.org/jira/browse/SOLR-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858191#comment-13858191 ] ASF subversion and git services commented on SOLR-5577: --- Commit

[jira] [Commented] (SOLR-5577) indexing delay due to zookeeper election

[ https://issues.apache.org/jira/browse/SOLR-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858190#comment-13858190 ] ASF subversion and git services commented on SOLR-5577: --- Commit

[JENKINS] Lucene-Solr-4.x-MacOSX (64bit/jdk1.7.0) - Build # 1139 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-4.x-MacOSX/1139/ Java: 64bit/jdk1.7.0 -XX:-UseCompressedOops -XX:+UseParallelGC All tests passed Build Log: [...truncated 10238 lines...] [junit4] JVM J0: stderr was not empty, see:

[jira] [Commented] (SOLR-5496) We should share an http connection manager across most non search httpclients and ensure all http connection managers get shutdown.

[ https://issues.apache.org/jira/browse/SOLR-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858195#comment-13858195 ] ASF subversion and git services commented on SOLR-5496: --- Commit

[jira] [Commented] (SOLR-5496) We should share an http connection manager across most non search httpclients and ensure all http connection managers get shutdown.

[ https://issues.apache.org/jira/browse/SOLR-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858196#comment-13858196 ] ASF subversion and git services commented on SOLR-5496: --- Commit

[jira] [Commented] (SOLR-5496) We should share an http connection manager across most non search httpclients and ensure all http connection managers get shutdown.

[ https://issues.apache.org/jira/browse/SOLR-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858198#comment-13858198 ] ASF subversion and git services commented on SOLR-5496: --- Commit

[jira] [Updated] (SOLR-5496) We should share an http connection manager across most non search httpclients and ensure all http connection managers get shutdown.

[ https://issues.apache.org/jira/browse/SOLR-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-5496: -- Fix Version/s: 4.6.1 We should share an http connection manager across most non search httpclients

[jira] [Updated] (SOLR-5550) shards.info is not returned in case of short circuited distributed query

[ https://issues.apache.org/jira/browse/SOLR-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Potter updated SOLR-5550: - Attachment: SOLR-5550.patch Here's a first cut of a solution to this issue w/o unit test. I

[JENKINS-MAVEN] Lucene-Solr-Maven-trunk #1064: POMs out of sync

Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/1064/ 3 tests failed. REGRESSION: org.apache.solr.morphlines.cell.SolrCellMorphlineTest.testSolrCellDocumentTypes Error Message: key:ignored_creation_date expected:[2011-09-02T10:11:00Z] but was:[๒๐๑๑-๐๙-๐๒T๑๐:๑๑:๐๐Z] Stack Trace:

[jira] [Created] (LUCENE-5379) Kurdish Analyzer

Robert Muir created LUCENE-5379: --- Summary: Kurdish Analyzer Key: LUCENE-5379 URL: https://issues.apache.org/jira/browse/LUCENE-5379 Project: Lucene - Core Issue Type: New Feature

[jira] [Updated] (LUCENE-5379) Kurdish Analyzer

[ https://issues.apache.org/jira/browse/LUCENE-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-5379: Attachment: LUCENE-5379.patch Kurdish Analyzer Key:

[jira] [Updated] (LUCENE-5379) Kurdish Analyzer

[ https://issues.apache.org/jira/browse/LUCENE-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-5379: Attachment: ckbtestdata.zip Vocabulary data zip Kurdish Analyzer

[jira] [Commented] (LUCENE-5339) Simplify the facet module APIs

[ https://issues.apache.org/jira/browse/LUCENE-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858276#comment-13858276 ] Shai Erera commented on LUCENE-5339: It's just that we have *.facet.taxonomy package,

[jira] [Comment Edited] (LUCENE-5339) Simplify the facet module APIs

[ https://issues.apache.org/jira/browse/LUCENE-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858276#comment-13858276 ] Shai Erera edited comment on LUCENE-5339 at 12/29/13 7:48 AM:

[jira] [Commented] (LUCENE-5339) Simplify the facet module APIs

[ https://issues.apache.org/jira/browse/LUCENE-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858279#comment-13858279 ] Robert Muir commented on LUCENE-5339: - Maybe one crazy idea is to look at the JDK