[
https://issues.apache.org/jira/browse/SOLR-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856087#action_12856087
]
Mark Miller commented on SOLR-1873:
---
As I wrap up the remaining work here, one i
[
https://issues.apache.org/jira/browse/SOLR-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-632.
--
Assignee: Mark Miller (was: Erik Hatcher)
Resolution: Fixed
I'm going to call this done - w
[
https://issues.apache.org/jira/browse/SOLR-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1873:
--
Attachment: SOLR-1873.patch
I had missed merging necessary changes to QueryElevation component - this
[
https://issues.apache.org/jira/browse/SOLR-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-1327.
---
Fix Version/s: (was: 1.5)
Resolution: Duplicate
> Allow special Filters to access, mod
[
https://issues.apache.org/jira/browse/SOLR-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-1436.
---
Assignee: Mark Miller
Resolution: Fixed
Hmm...the description of this is messed up -
anyway
[
https://issues.apache.org/jira/browse/SOLR-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855781#action_12855781
]
Mark Miller commented on SOLR-1851:
---
I didnt take the setting out
solr/con
[
https://issues.apache.org/jira/browse/SOLR-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-1534.
---
Resolution: Fixed
did this some time ago
> Remove QueryWrap
[
https://issues.apache.org/jira/browse/SOLR-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-1851.
---
Resolution: Fixed
> luceneAutoCommit no longer has any effect - remove it from con
[
https://issues.apache.org/jira/browse/SOLR-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855765#action_12855765
]
Mark Miller edited comment on SOLR-1873 at 4/11/10 5:14 PM:
[
https://issues.apache.org/jira/browse/SOLR-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1873:
--
Attachment: SOLR-1873.patch
Up to trunk and clean up some tests...all tests pass but commits remain
[
https://issues.apache.org/jira/browse/SOLR-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-1839.
---
Assignee: Mark Miller
Resolution: Fixed
> If the stress tests in BaseDistributedSearchTestC
[
https://issues.apache.org/jira/browse/SOLR-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-1840.
---
Assignee: Mark Miller
Resolution: Fixed
> DistributedSpellCheckComponentTest appears
[
https://issues.apache.org/jira/browse/SOLR-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1840:
--
Attachment: SOLR-1840.patch
Because each query would trigger a spellcheck index rebuild, the test was
Investigate unclosed Reader in IndexBasedSpellCheck
---
Key: SOLR-1877
URL: https://issues.apache.org/jira/browse/SOLR-1877
Project: Solr
Issue Type: Bug
Reporter: Mark Miller
[
https://issues.apache.org/jira/browse/SOLR-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1877:
--
Component/s: spellchecker
> Investigate unclosed Reader in IndexBasedSpellCh
[
https://issues.apache.org/jira/browse/SOLR-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855662#action_12855662
]
Mark Miller commented on SOLR-1873:
---
Sweet - all tests now pass - done to just
[
https://issues.apache.org/jira/browse/SOLR-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1873:
--
Attachment: SOLR-1873.patch
fixes the distrib spellcheck failure
> Commit Solr Cloud to tr
[
https://issues.apache.org/jira/browse/SOLR-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1873:
--
Attachment: zookeeper-3.2.2.jar
log4j-over-slf4j-1.5.5.jar
> Commit Solr Cloud to tr
[
https://issues.apache.org/jira/browse/SOLR-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1873:
--
Attachment: SOLR-1873.patch
Still a lot to do, but after a couple days work, getting pretty close
Commit Solr Cloud to trunk
--
Key: SOLR-1873
URL: https://issues.apache.org/jira/browse/SOLR-1873
Project: Solr
Issue Type: New Feature
Affects Versions: 1.4
Reporter: Mark Miller
Assignee
[
https://issues.apache.org/jira/browse/SOLR-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855127#action_12855127
]
Mark Miller commented on SOLR-1238:
---
isRepeatable means the payload stream can be
I'd like to merge solr cloud into trunk -
I think there may be some more polish to do, but its pretty close, and
back compatible if you choose not to run in "zookeeper" mode.
I think the next step for this first phase (there are still many
features to add) is to get it in trunk so we can get
FYI:
Uwe is going to merge the Lucene flex branch soon, and as a result, Solr
trunk will very briefly have an issue:
https://issues.apache.org/jira/browse/LUCENE-2370
--
- Mark
http://www.lucidimagination.com
[
https://issues.apache.org/jira/browse/SOLR-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1866:
--
Attachment: SOLR-1866.patch
Another possible fix. Simple - but includes some libs that don't act
Issue Type: Bug
Reporter: Mark Miller
Priority: Minor
The JettyWebappTest straddles example and src/webapp in a way that the Plugin
classloader's parent WebappClassloader points to src/webapp which has no libs
dir. This can cause problems - eg its a problem with the cu
[
https://issues.apache.org/jira/browse/SOLR-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1801:
--
Issue Type: Improvement (was: Bug)
Not sure if it was this guy or not, but someone was on the user
[
https://issues.apache.org/jira/browse/SOLR-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-1659.
---
Resolution: Fixed
this is resolved on the new merged lucene/solr trunk (part of first update)
>
[
https://issues.apache.org/jira/browse/SOLR-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1851:
--
Attachment: SOLR-1851.patch
> luceneAutoCommit no longer has any effect - remove it from con
Reporter: Mark Miller
Assignee: Mark Miller
Priority: Minor
Fix For: 1.5
missed this on the upgrade to Lucene trunk - Lucene no longer has autocommit -
so it now has no effect in Solr - needs to be removed with a warning if its
found.
--
This message is
[
https://issues.apache.org/jira/browse/SOLR-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850539#action_12850539
]
Mark Miller commented on SOLR-896:
--
Yeah, I'll try and do that soon.
Chris was
Yeah, there are things we can do to improve some of this (uptodatetask
or something?) - Uwe has some ideas the other day.
- Mark
http://www.lucidimagination.com (mobile)
On Mar 26, 2010, at 1:53 AM, Robert Muir wrote:
I noticed that for whatever reason, solr's build.xml doesnt detect if
lu
On 03/25/2010 11:27 AM, Mark Miller wrote:
On 03/25/2010 11:22 AM, Igor Motov wrote:
I wonder if it would make sense to replace log4j-1.2.15.jar in the lib
directory of the cloud branch with log4j-over-slf4j-1.5.5.jar. SOLR is
already using SLF4J for its logging and log4j-over-slf4j bridge
On 03/25/2010 11:22 AM, Igor Motov wrote:
I wonder if it would make sense to replace log4j-1.2.15.jar in the lib
directory of the cloud branch with log4j-over-slf4j-1.5.5.jar. SOLR is
already using SLF4J for its logging and log4j-over-slf4j bridge would
redirect all ZooKeeper log messages into th
On 03/24/2010 06:43 PM, Igor Motov wrote:
I was experimenting with the latest (r919455) revision of the cloud branch
and noticed a dependency between CloudSolrServer and ZkController. It looks
like CloudSolrServer is still using two constants from ZkController:
NODE_NAME and URL_PROP. After movin
Issue Type: Bug
Components: spellchecker
Reporter: Mark Miller
Fix For: 1.5
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/SOLR-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848985#action_12848985
]
Mark Miller commented on SOLR-1840:
---
The following exceptions were thrown by thr
[
https://issues.apache.org/jira/browse/SOLR-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848986#action_12848986
]
Mark Miller commented on SOLR-1840:
---
See the linked issue to enable this test fai
[
https://issues.apache.org/jira/browse/SOLR-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1839:
--
Attachment: SOLR-1839.patch
This patch will expose the issue and the Distrib spelling component test
Issue Type: Bug
Reporter: Mark Miller
Fix For: 1.5
In the past, you would not likely notice these failures at all - as they would
not be printed to the console, but rather just go to the test-results.
--
This message is automatically generated by JIRA.
-
You can
[
https://issues.apache.org/jira/browse/SOLR-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848332#action_12848332
]
Mark Miller commented on SOLR-632:
--
I'm trying out this upgrade (to 6.1.22) on
://issues.apache.org/jira/browse/SOLR-1833
Project: Solr
Issue Type: Improvement
Affects Versions: 1.4
Reporter: Mark Miller
Priority: Minor
Fix For: 1.5
In many cases I wouldn't want to come up with every file I want hidden -
especially when new
On 03/18/2010 09:27 PM, Chris Hostetter wrote:
: Sorry about the following non serious reply:
:
: It hasn't seemed to hurt the most popular software in the world to be way
: worse than that ;)
:
: 1, 2, 3, NT, 95, 98, 98SE, ME, CE, 2000, XP, 2003, Vista, 2008, 7 (by who's
a) 2000 came out before
[
https://issues.apache.org/jira/browse/SOLR-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847176#action_12847176
]
Mark Miller commented on SOLR-1817:
---
bq. Maybe we should just kill the whole con
On 03/18/2010 02:49 PM, Chris Hostetter wrote:
Use 3.1 and developers in the know will understand that i's because we're
using LuceneJava 3.1; but uninformed users *might* be confused as to why
it jumped to a (seemingly) arbitrary number.
Sorry about the following non serious reply:
It has
th
Lucene and Solr.
Thanks to everyone that contributed to getting all this working!
--
- Mark
http://www.lucidimagination.com
On 03/17/2010 12:40 PM, Mark Miller wrote:
Okay, so this looks good to me (a few others seemed to like it -
though Lucene-Dev was somehow dropped earlier) - lets tr
On 03/17/2010 12:46 PM, Robert Muir wrote:
On Wed, Mar 17, 2010 at 12:40 PM, Mark Miller wrote:
Okay, so this looks good to me (a few others seemed to like it - though
Lucene-Dev was somehow dropped earlier) - lets try this out on the branch?
(then we can get rid of that "horrible&qu
Okay, so this looks good to me (a few others seemed to like it - though
Lucene-Dev was somehow dropped earlier) - lets try this out on the
branch? (then we can get rid of that "horrible" branch name ;) )
Anyone on the current branch object to having to do a quick svn switch?
On 03/16/2010 06:4
[
https://issues.apache.org/jira/browse/SOLR-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846244#action_12846244
]
Mark Miller commented on SOLR-1817:
---
U - I'm sorry - I'm being confusi
[
https://issues.apache.org/jira/browse/SOLR-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846242#action_12846242
]
Mark Miller commented on SOLR-1817:
---
bq. That is the issue where that possible NP
[
https://issues.apache.org/jira/browse/SOLR-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846240#action_12846240
]
Mark Miller commented on SOLR-1817:
---
bq. In either case: why do we need to specif
[
https://issues.apache.org/jira/browse/SOLR-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846225#action_12846225
]
Mark Miller commented on SOLR-1817:
---
bq. why is "admin" suddenly a magic a
[
https://issues.apache.org/jira/browse/SOLR-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846219#action_12846219
]
Mark Miller commented on SOLR-1817:
---
bq. two of the places you removed "
[
https://issues.apache.org/jira/browse/SOLR-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846208#action_12846208
]
Mark Miller commented on SOLR-1817:
---
1 and 2) I agree - this is part of the big
On 03/16/2010 06:46 PM, Chris Hostetter wrote:
Here's my concrete suggestion that could be done today
+1
--
- Mark
http://www.lucidimagination.com
[
https://issues.apache.org/jira/browse/SOLR-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845697#action_12845697
]
Mark Miller commented on SOLR-1803:
---
bq. Actually the problem is that the effec
On 03/15/2010 11:28 PM, Yonik Seeley wrote:
So, we have a few options on where to put Solr's new trunk:
Solr moves to Lucene's trunk:
/java/trunk, /java/trunk/sol
+1. With the goal of merged dev, merged tests, this looks the best to
me. Simple to do patches that span both, simple to setup
Sorry - hit a bad keyboard short cut and sent this mid way through
writing it - please disregard and read the followup.
On 03/15/2010 07:21 PM, Mark Miller wrote:
On 03/15/2010 07:14 PM, Chris Hostetter wrote:
: Development on branches/solr to get on lucene trunk is progressing at
: a furious
On 03/15/2010 07:14 PM, Chris Hostetter wrote:
: Development on branches/solr to get on lucene trunk is progressing at
: a furious (nay... ferocious) pace, pushed by the "not new, but new to
: solr" committers. Feels great to have everyone on the same team!
I feel like i must have missed out on
On 03/15/2010 05:24 PM, Paul Borgermans wrote:
On Mon, Mar 15, 2010 at 9:39 PM, Robert Muir wrote:
Hello,
Is there any concern with removing the deprecated HtmlStrip*Tokenizer factories?
Maybe a communication issue, you need to read the source code or
javadocs to know it is depreca
[
https://issues.apache.org/jira/browse/SOLR-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845013#action_12845013
]
Mark Miller commented on SOLR-1817:
---
Just did a check - solr.xml errors will als
[
https://issues.apache.org/jira/browse/SOLR-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1817:
--
Attachment: SOLR-1817.patch
More of the solution. If you access localhost:8983/solr it will now show
Project: Solr
Issue Type: Bug
Components: contrib - DataImportHandler
Reporter: Mark Miller
Priority: Trivial
Fix For: 1.5
Looking like we should do something if DOT_PATTERN does not match a primary key
(rather then get the resulting
On 03/13/2010 06:26 PM, Mark Miller wrote:
I don't really follow DataImportHandler, but it looks like its using
an unbounded cache (simple HashMap).
Perhaps we should make the cache size configurable?
The impl seems a little odd - the caching occurs in the base class -
so caching impls
[
https://issues.apache.org/jira/browse/SOLR-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1817:
--
Attachment: SOLR-1817.patch
Okay, prob done playing for a bit - this patch mostly fixes the issue where
[
https://issues.apache.org/jira/browse/SOLR-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844951#action_12844951
]
Mark Miller commented on SOLR-1817:
---
current patch - still doesn't work rig
[
https://issues.apache.org/jira/browse/SOLR-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1817:
--
Attachment: SOLR-1817.patch
> Fix Solr error reporting to work correctly with multic
Reporter: Mark Miller
Priority: Minor
Fix For: 1.5
Attachments: SOLR-1817.patch
Here is a rough patch that attempts to fix how error reporting works with
multi-core (not in terms of logs, but what you see on an http request).
The patch is not done
[
https://issues.apache.org/jira/browse/SOLR-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844227#action_12844227
]
Mark Miller commented on SOLR-1743:
---
This looks good to me as a first step - tested
[
https://issues.apache.org/jira/browse/SOLR-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843855#action_12843855
]
Mark Miller commented on SOLR-1802:
---
Hey John,
Depending on what you are trying t
[
https://issues.apache.org/jira/browse/SOLR-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1659:
--
Attachment: SOLR-1659.patch
To trunk - updates things that have changed, and some previous workarounds
[
https://issues.apache.org/jira/browse/SOLR-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843611#action_12843611
]
Mark Miller commented on SOLR-1674:
---
I've committed the speed up patch, than
[
https://issues.apache.org/jira/browse/SOLR-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843372#action_12843372
]
Mark Miller commented on SOLR-1803:
---
Strike number one - didn't realize that
[
https://issues.apache.org/jira/browse/SOLR-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843367#action_12843367
]
Mark Miller commented on SOLR-1803:
---
A few comments:
1. If you want to test multi-va
[
https://issues.apache.org/jira/browse/SOLR-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843357#action_12843357
]
Mark Miller commented on SOLR-1807:
---
bq. I guess the only way is to change
[
https://issues.apache.org/jira/browse/SOLR-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843355#action_12843355
]
Mark Miller commented on SOLR-1743:
---
So from what I can see - the immediate problem
[
https://issues.apache.org/jira/browse/SOLR-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843227#action_12843227
]
Mark Miller commented on SOLR-1743:
---
Okay, I sat down and thought about what we shoul
[
https://issues.apache.org/jira/browse/SOLR-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842728#action_12842728
]
Mark Miller commented on SOLR-1812:
---
I do not agree that this is a correct use of the
Issue Type: Bug
Components: clients - java
Affects Versions: 1.4
Reporter: Mark Miller
Priority: Minor
Fix For: 1.5
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/SOLR-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-1722.
---
Resolution: Fixed
> Allowing changing the "special" default core name, and as a de
[
https://issues.apache.org/jira/browse/SOLR-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841844#action_12841844
]
Mark Miller commented on SOLR-1808:
---
Right - thats how its supposed to work - we d
For those committers that don't follow the general mailing list, or
follow it that closely, we are currently having a vote for committers:
http://search.lucidimagination.com/search/document/4722d3144c2e3a8b/vote_merge_lucene_solr_development
--
- Mark
http://www.lucidimagination.com
[
https://issues.apache.org/jira/browse/SOLR-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1722:
--
Attachment: SOLR-1722.patch
I'm going to commit this fix a little later today.
> Allowing chan
[
https://issues.apache.org/jira/browse/SOLR-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840748#action_12840748
]
Mark Miller edited comment on SOLR-1722 at 3/3/10 5:39 PM:
---
s
[
https://issues.apache.org/jira/browse/SOLR-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reopened SOLR-1722:
---
small bug - defaultCoreName is looked for at /solr, but should be /solr/cores -
also, defaultCoreName
[
https://issues.apache.org/jira/browse/SOLR-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840177#action_12840177
]
Mark Miller commented on SOLR-1743:
---
Hoss - I've got to digest and respond to
[
https://issues.apache.org/jira/browse/SOLR-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1743:
--
Attachment: SOLR-1743.patch
Here is a quick attempt at solving most of the rest of this.
The idea is
[
https://issues.apache.org/jira/browse/SOLR-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1743:
--
Attachment: SOLR-1743.patch
Well its no surprise that I'm confusing...
But I swear I tested
On 02/27/2010 05:53 AM, Shalin Shekhar Mangar wrote:
Any objections?
Didn't rc2 (that we are on) end up being the final release?
--
- Mark
http://www.lucidimagination.com
The SolrRequestHandler page is generating some odd wiki links:
Under List of Request Handlers Available we use:
<-title:CategorySolrRequestHandler)>>
But thats bring up a non relevant german and what looks like japanese page:
1. CategoryCategory
2. DataImportHandler
3. DisMa
Have you removed the QueryElevationComponent from the solrconfig? It
requires a unique field in schema, and that its a String type.
--
- Mark
http://www.lucidimagination.com
Erick Erickson wrote:
> This may be related to SOLR-1742 and/or SOLR-1743.
>
> I have a minimal schema file, 4 fields
[
https://issues.apache.org/jira/browse/SOLR-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834052#action_12834052
]
Mark Miller commented on SOLR-1774:
---
We could just add it to the classes that are all
[
https://issues.apache.org/jira/browse/SOLR-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1770:
--
Attachment: SOLR-1770.patch
initial patch (won't do it form a patch to handle the moves though)
&
Affects Versions: 1.4
Reporter: Mark Miller
Fix For: 1.5
This is a better starting point for adding more cores - perhaps we can also get
rid of multi-core example
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the
[
https://issues.apache.org/jira/browse/SOLR-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-1722.
---
Resolution: Fixed
> Allowing changing the "special" default core name, and as a de
[
https://issues.apache.org/jira/browse/SOLR-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830943#action_12830943
]
Mark Miller commented on SOLR-1722:
---
If no one objects, I'd like to commit thi
[
https://issues.apache.org/jira/browse/SOLR-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1743:
--
Attachment: SOLR-1743.patch
Fixes the "at least one core has abortOnConfigError = true&
[
https://issues.apache.org/jira/browse/SOLR-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830271#action_12830271
]
Mark Miller commented on SOLR-1743:
---
Not quite as bad as I thought - I guess thi
[
https://issues.apache.org/jira/browse/SOLR-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829828#action_12829828
]
Mark Miller commented on SOLR-1743:
---
bq. ... I'll take a whack at a fix.
Heh -
[
https://issues.apache.org/jira/browse/SOLR-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reassigned SOLR-1743:
-
Assignee: Mark Miller
I think this was always a bug with MultiCore and single core worked. Now
[
https://issues.apache.org/jira/browse/SOLR-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-1756.
---
Resolution: Fixed
Thanks a lot Christoph!
> the date.format setting does not w
1 - 100 of 774 matches
Mail list logo