[
https://issues.apache.org/jira/browse/LUCENE-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14059683#comment-14059683
]
Hunts Chen commented on LUCENE-5057:
HI [~lukas.vlcek]
How do you solve the problem
[
https://issues.apache.org/jira/browse/LUCENE-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir closed LUCENE-5057.
---
Closing issue: guys, its a morphological analyzer. That means you get all the
possibilities. This is
[
https://issues.apache.org/jira/browse/SOLR-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14059771#comment-14059771
]
Maciej Zasada commented on SOLR-5746:
-
bq. 1) can you explain why the need for the new
Hello,
I am interested in creating and running Solr analyzer chains outside
of normal process (no live Solr). Just construct a chain, feed it
tokens and see what happens.
I would appreciate any hints on what that takes and whether there are
any hidden/weird dependencies (e.g. for resource
[
https://issues.apache.org/jira/browse/SOLR-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14059805#comment-14059805
]
Jack Krupansky commented on SOLR-5746:
--
Will the changes for this issue result in a
Tracing through indexing or query parsing is... a challenge. Start with
something simpler like the analysis admin API.
See:
http://lucene.apache.org/solr/4_9_0/solr-core/org/apache/solr/handler/FieldAnalysisRequestHandler.html
-- Jack Krupansky
-Original Message-
From: Alexandre
Uhm. That's where I did start. :-(
Personal: http://www.outerthoughts.com/ and @arafalov
Solr resources: http://www.solr-start.com/ and @solrstart
Solr popularizers community: https://www.linkedin.com/groups?gid=6713853
On Sat, Jul 12, 2014 at 9:50 PM, Jack Krupansky j...@basetechnology.com
H, I think it's reasonably straightforward to construct what
is implied by a Solr analysis chain in Lucene, would that do? Or
do you want to read a schema.xml file outside Solr?
If the former, then you can pretty much skip the Solr code entirely.
FWIW,
Erick
On Sat, Jul 12, 2014 at 6:59 AM,
Hi,
H, I think it's reasonably straightforward to construct what is implied
by a Solr analysis chain in Lucene, would that do? Or do you want to read a
schema.xml file outside Solr?
If the former, then you can pretty much skip the Solr code entirely.
Read this:
[
https://issues.apache.org/jira/browse/SOLR-6235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-6235:
Attachment: SOLR-6235.patch
Patch which uses coreNodeName instead of coreName for
[
https://issues.apache.org/jira/browse/SOLR-6235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14059845#comment-14059845
]
Shalin Shekhar Mangar commented on SOLR-6235:
-
I fixed another mistake that I
Shalin Shekhar Mangar created SOLR-6240:
---
Summary: ZkStateReader.getReplicaProps has an unused coreName
parameter
Key: SOLR-6240
URL: https://issues.apache.org/jira/browse/SOLR-6240
Project:
I don't want to read the schema.xml, but I do want to create factories
using the same parameters they use in schema. So, it looks like I need
to play around with ResourceLoaders and maybe SPI loaders, so things
like wordlists get loaded.
Starting from FieldAnalyzer turned out to be a dead-end
The factories are part of Lucene, Solr is just using them. To list of available
factories (in classpath) use
(Tokenizer|TokenFilter|CharFilter)Factory.availableX() methods (to list all
their names). You can invoke them using the corresponding forName() method and
build an Analyzer from
[
https://issues.apache.org/jira/browse/SOLR-6235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-6235:
Attachment: SOLR-6235.patch
I improved logging by adding coreName as well as
[
https://issues.apache.org/jira/browse/SOLR-6235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14059892#comment-14059892
]
ASF subversion and git services commented on SOLR-6235:
---
Commit
[
https://issues.apache.org/jira/browse/SOLR-6235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14059894#comment-14059894
]
ASF subversion and git services commented on SOLR-6235:
---
Commit
[
https://issues.apache.org/jira/browse/SOLR-5596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar reassigned SOLR-5596:
---
Assignee: Shalin Shekhar Mangar (was: Mark Miller)
Shalin Shekhar Mangar created SOLR-6241:
---
Summary: HttpPartitionTest.testRf3WithLeaderFailover fails
sometimes
Key: SOLR-6241
URL: https://issues.apache.org/jira/browse/SOLR-6241
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14059896#comment-14059896
]
Shalin Shekhar Mangar commented on SOLR-6241:
-
I have looked at this test and
[
https://issues.apache.org/jira/browse/SOLR-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14059898#comment-14059898
]
ASF subversion and git services commented on SOLR-6240:
---
Commit
[
https://issues.apache.org/jira/browse/SOLR-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14059900#comment-14059900
]
ASF subversion and git services commented on SOLR-6240:
---
Commit
[
https://issues.apache.org/jira/browse/SOLR-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14059902#comment-14059902
]
ASF subversion and git services commented on SOLR-6240:
---
Commit
[
https://issues.apache.org/jira/browse/SOLR-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar resolved SOLR-6240.
-
Resolution: Fixed
Assignee: Shalin Shekhar Mangar
[
https://issues.apache.org/jira/browse/SOLR-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14059903#comment-14059903
]
ASF subversion and git services commented on SOLR-6240:
---
Commit
That sounds like a wonderful project, Alexandre — I’ve always wanted such a
capability!
I suggest approaching this very pragmatically based on minimizing the time
to get something useful, which means leveraging as much as is available
already — that means solr’s existing analysis UI screen. I
Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/1166/
7 tests failed.
REGRESSION: org.apache.solr.cloud.CustomCollectionTest.testDistribSearch
Error Message:
expected:0 but was:3
Stack Trace:
java.lang.AssertionError: expected:0 but was:3
at
[
https://issues.apache.org/jira/browse/LUCENE-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14059951#comment-14059951
]
Ramkumar Aiyengar commented on LUCENE-5057:
---
Isn't edismax generating an
[
https://issues.apache.org/jira/browse/SOLR-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar reopened SOLR-6240:
-
The patch that I committed wasn't complete and it broke some of the tests.
[
https://issues.apache.org/jira/browse/SOLR-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14059956#comment-14059956
]
ASF subversion and git services commented on SOLR-6240:
---
Commit
[
https://issues.apache.org/jira/browse/SOLR-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14059957#comment-14059957
]
ASF subversion and git services commented on SOLR-6240:
---
Commit
This was due to SOLR-6240. I committed a fix.
On Sun, Jul 13, 2014 at 4:13 AM, Apache Jenkins Server
jenk...@builds.apache.org wrote:
Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/1166/
7 tests failed.
REGRESSION: org.apache.solr.cloud.CustomCollectionTest.testDistribSearch
[
https://issues.apache.org/jira/browse/SOLR-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar resolved SOLR-6240.
-
Resolution: Fixed
Fix Version/s: 5.0
ZkStateReader.getReplicaProps has an
Hmmm, sounds pretty cool!
I wonder if it would be sufficient, for the first cut anyway, to let the user
specify whatever was necessary to bypass all the ResourceLoader stuff,
why make the user put the files in a place Solr knows about? Instead, for
development, it might be sufficient (and less
[
https://issues.apache.org/jira/browse/SOLR-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14059985#comment-14059985
]
Varun Thacker commented on SOLR-6177:
-
SolrLogLayout adds core name but in it's short
Right,
For the first cut, I am not planning to let people to edit things like
synonyms files. Just select from a pre-existing list/dropdown. And
I'll most probably start by providing a bunch of fixed stacks taken
from example schemas. So, none of the Solr's flexibility is requited,
just need to
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/10802/
Java: 64bit/jdk1.8.0_20-ea-b21 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC
1 tests failed.
REGRESSION: org.apache.solr.core.TestArbitraryIndexDir.testLoadNewIndexDir
Error Message:
Error opening new searcher
Stack Trace:
37 matches
Mail list logo
