[
https://issues.apache.org/jira/browse/SOLR-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503660#comment-13503660
]
Ari Maniatis commented on SOLR-3304:
Thanks David. I've asked my developer to follow up
Hi
Before upgrading to Solr 4.0.0 we used to handle our collection creation
ourselves, by creating each shards through the low-level CoreAdmin API.
We used to create multiple shards under the same collection on each Solr
server. Performance tests has shown that this is a good idea, and it is
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503763#comment-13503763
]
Dominik Siebel commented on SOLR-2141:
--
[~jdyer]
After I finally had some time to
The Collections API was fairly rushed - so that 4.0 had something easier than
the CoreAdmin API.
Due to that, it has a variety of limitations:
1. It only picks instances for a collection one way - randomly from the list of
live instances. This means it's no good for multiple shards on the same
2012/11/23 Simone Gianni simo...@apache.org
3) how does creation/synchronization of a new replica happens? (so where
should I have to plug to replicate also the external files)
As far as i understood, SolrCloud forwards add/update to connected
replicas, but when a replica starts up it uses
[
https://issues.apache.org/jira/browse/SOLR-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503807#comment-13503807
]
Yonik Seeley commented on SOLR-2592:
Hi Michael, while I was reviewing your patch, I
[
https://issues.apache.org/jira/browse/SOLR-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503807#comment-13503807
]
Yonik Seeley edited comment on SOLR-2592 at 11/26/12 2:44 PM:
--
ant precommit will check if the source tree is dirty (i.e. contains files
not in source control) and stop with a failure if so. I find that rather
annoying since I've usually got a variety of .patch files and IDE config
changes. What is the rationale behind this check? How do people usually
Deniz Durmus created SOLR-4112:
--
Summary: Dataimporting with SolrCloud Fails
Key: SOLR-4112
URL: https://issues.apache.org/jira/browse/SOLR-4112
Project: Solr
Issue Type: Bug
Affects
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503815#comment-13503815
]
Dominik Siebel commented on SOLR-2141:
--
Hi [~jdyer],
I just worked through the changes
Mark Miller skrev:
The Collections API was fairly rushed - so that 4.0 had something easier than
the CoreAdmin API.
Yes I see. Our collection-creation code is more sophisticated than
yours. We probably would like to migrate to the Solr Collection API now
anyway - to be using it already
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503828#comment-13503828
]
James Dyer commented on SOLR-2141:
--
Dominik,
Can you confirm for me that with the current
[
https://issues.apache.org/jira/browse/SOLR-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503837#comment-13503837
]
Mark Miller commented on SOLR-2592:
---
bq. Now, currently the ClusterState object is
[
https://issues.apache.org/jira/browse/SOLR-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503839#comment-13503839
]
Yonik Seeley commented on SOLR-2592:
bq. the Overseer could probably grab this from the
On Mon, Nov 26, 2012 at 9:55 AM, Per Steffensen st...@designware.dk wrote:
Well I would like to jump in with respect to making support for running
several shards of the same collection on the same instance, it is just so
damn hard to get you to commit stuff :-)
A lot of the problem is time
I think the idea is to catch files you forgot to svn add.
For IDE files, you should just svn ignore them?
Mike McCandless
http://blog.mikemccandless.com
On Mon, Nov 26, 2012 at 9:46 AM, David Smiley (@MITRE.org)
dsmi...@mitre.org wrote:
ant precommit will check if the source tree is dirty
[
https://issues.apache.org/jira/browse/SOLR-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer updated SOLR-4112:
-
Attachment: SOLR-4112.patch
Please try the attached patch and let me know if this fixes your issue. This
I agree this (skipping a commit if there seems to be no changes) is annoying.
I think a separate API would make sense? Then we'd just set the
changed bit in IW so that the next commit we always write it.
Mike McCandless
http://blog.mikemccandless.com
On Sat, Nov 24, 2012 at 12:08 AM, Shai
I will open an issue so we can continue discussing.
Shai
On Mon, Nov 26, 2012 at 6:17 PM, Michael McCandless
luc...@mikemccandless.com wrote:
I agree this (skipping a commit if there seems to be no changes) is
annoying.
I think a separate API would make sense? Then we'd just set the
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503879#comment-13503879
]
Dominik Siebel commented on SOLR-2141:
--
Checked with
git-svn-id:
[
https://issues.apache.org/jira/browse/SOLR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey updated SOLR-1972:
---
Attachment: SOLR-1972_metrics.patch
The r1413047 commit caused a minor hiccup for this patch against
Of course I understand everything you say. We are just using Solr very
intensively in my current project and we want to do big changes and when
we make them we test them very thoroughly - so we are pretty sure they
work as they are supposed to, but of course that is hard to see on your
side,
On Nov 26, 2012, at 11:51 AM, Per Steffensen st...@designware.dk wrote:
I am a very experinced programmer with a long record as architect, designer,
mentor etc. Is there a chance that I could become committer? You will end up
happy - and so will I! :-)
You have to build up enough merit in
Shai Erera created LUCENE-4575:
--
Summary: Allow IndexWriter to commit, even just commitData
Key: LUCENE-4575
URL: https://issues.apache.org/jira/browse/LUCENE-4575
Project: Lucene - Core
Issue
Hello there,
I'm confused about soft commit. There is very little explanation about
this on wiki, I hope to know some more details.
Thanks in advance.
Best Regards,
Illu
This is still a problem for people working with git-svn, but I admit
it makes sense to have a precommit target that assumes a supported
configuration, whatever it may be, and enforces strict checks rather
than support multiple configurations with next to nothing.
Dawid
On Mon, Nov 26, 2012 at
Hi David,
there are actually 2 reasons for this check:
- It prevents that you forget to add files before committing. We had this quite
often, causing unbuildable sources and Jenkins failures.
- Prevent test cases from leaving files around at wrong places. This was the
original idea behind the
I've always put patches up one level from checked out dirs: svn diff
../PROJECT-.patch; patch -p0 ../PROJECT-.patch.
For stuff that should be ignored by everybody (or that wouldn't cause trouble
for others), we could add them to the svn:ignore list for the directory they're
in?
[
https://issues.apache.org/jira/browse/SOLR-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503978#comment-13503978
]
Michael Garski commented on SOLR-2592:
--
bq. I realized that we want something that
AFAIK if you set svn:ignore * then it won't ignore files and directories that
are in source control.
~ David
On Nov 26, 2012, at 1:41 PM, sarowe [via Lucene] wrote:
I've always put patches up one level from checked out dirs: svn diff
../PROJECT-.patch; patch -p0 ../PROJECT-.patch.
Alan and everybody,
How do you feel about it?
Feedback is quite appreciated!
On Fri, Nov 16, 2012 at 1:02 AM, Mikhail Khludnev
mkhlud...@griddynamics.com wrote:
Alan,
Please find the patch attached
https://issues.apache.org/jira/browse/SOLR-4085
Regards
On Wed, Nov 14, 2012 at
I guess there are two classes of things here: new non-ignored
non-svn-controlled files; and modifications to svn-controlled files.
My point about svn:ignore was that we could use it to handle the non-ignored
non-svn-controlled files case.
I guess you're talking about the svn-controlled
[
https://issues.apache.org/jira/browse/SOLR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Woodward resolved SOLR-1972.
-
Resolution: Fixed
Committed to branch 4x, r1413797
Thanks for prodding, Shawn!
Ok thanks. Guess you are not ready to nominate me for now. But who are
the nominators? Are you a nominator, Mark? And how to get nominated - do
I have to ask (as I did today) or do I just have to wait until a
nominator gets the idea about me as a committer by himself?
Regards, Per Steffensen
[
https://issues.apache.org/jira/browse/SOLR-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504033#comment-13504033
]
Yonik Seeley commented on SOLR-2592:
FWIW, I'm trying out github for this patch.
My
If svn:ignore is set to '*' at the top level project, then ant precommit won't
complain about dirty files that exist there, such as patch files, notes to
myself, and whatever else. The wildcard should not conflict with build.xml or
the other few checked-in files and folders being in source
The nominators are generally the committers on the lucene and solr projects.
There is a list of those on the website under Who We Are. Yes, I am one. The
PMC then votes - there is also a list of who is on the PMC on the website.
The history is, generally you just wait to be nominated. Everyone
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer updated SOLR-2141:
-
Affects Version/s: 4.0
Fix Version/s: 5.0
4.1
Assignee: James
Mark,
Do I need to do anything for the bot to make its comment, aside from the
commit? I just made a commit to both branches. How much delay is there /
i.e. what's its schedule?
~ David
-
Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book
--
View this message in
Hi Dawid.
There's an ant build file that looks for Test*, *Test, and EXCLUDES '$'
hence no inner class.
I wish the test infrastructure simply scanned all test classes in test paths
for @Test or JUnit Testcase subclass. After all, the vast majority of
classes in /test/** are going to be tests. No
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer updated SOLR-2141:
-
Attachment: SOLR-2141.patch
I've attached a patch which fixes the functions namespace issue. More
[
https://issues.apache.org/jira/browse/SOLR-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504105#comment-13504105
]
James Dyer commented on SOLR-3842:
--
From Stackoverflow:
I'm trying to perform a
I wish the test infrastructure simply scanned all test classes in test paths
for @Test or JUnit Testcase subclass. After all, the vast majority of
classes in /test/** are going to be tests. No big deal.
This isn't entirely correct since Lucene tests may not be annotated
and may not subclass
[
https://issues.apache.org/jira/browse/SOLR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504138#comment-13504138
]
Commit Tag Bot commented on SOLR-1972:
--
[branch_4x commit] Alan Woodward
[
https://issues.apache.org/jira/browse/SOLR-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504139#comment-13504139
]
Commit Tag Bot commented on SOLR-1916:
--
[branch_4x commit] James Dyer
[
https://issues.apache.org/jira/browse/SOLR-4093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504140#comment-13504140
]
Commit Tag Bot commented on SOLR-4093:
--
[branch_4x commit] Yonik Seeley
[
https://issues.apache.org/jira/browse/SOLR-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504141#comment-13504141
]
Commit Tag Bot commented on SOLR-4111:
--
[branch_4x commit] James Dyer
[
https://issues.apache.org/jira/browse/SOLR-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504142#comment-13504142
]
Commit Tag Bot commented on SOLR-4101:
--
[branch_4x commit] Alan Woodward
[
https://issues.apache.org/jira/browse/LUCENE-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504143#comment-13504143
]
Commit Tag Bot commented on LUCENE-4570:
[branch_4x commit] Uwe Schindler
[
https://issues.apache.org/jira/browse/SOLR-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504144#comment-13504144
]
Commit Tag Bot commented on SOLR-2045:
--
[branch_4x commit] James Dyer
[
https://issues.apache.org/jira/browse/LUCENE-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504145#comment-13504145
]
Commit Tag Bot commented on LUCENE-3441:
[branch_4x commit] Shai Erera
[
https://issues.apache.org/jira/browse/LUCENE-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504146#comment-13504146
]
Commit Tag Bot commented on LUCENE-3441:
[branch_4x commit] Shai Erera
[
https://issues.apache.org/jira/browse/SOLR-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504147#comment-13504147
]
Commit Tag Bot commented on SOLR-4086:
--
[trunk commit] James Dyer
[
https://issues.apache.org/jira/browse/SOLR-4093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504149#comment-13504149
]
Commit Tag Bot commented on SOLR-4093:
--
[trunk commit] Yonik Seeley
[
https://issues.apache.org/jira/browse/SOLR-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504148#comment-13504148
]
Commit Tag Bot commented on SOLR-1916:
--
[trunk commit] James Dyer
[
https://issues.apache.org/jira/browse/SOLR-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504151#comment-13504151
]
Commit Tag Bot commented on SOLR-4101:
--
[trunk commit] Alan Woodward
[
https://issues.apache.org/jira/browse/LUCENE-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504152#comment-13504152
]
Commit Tag Bot commented on LUCENE-4570:
[trunk commit] Uwe Schindler
[
https://issues.apache.org/jira/browse/SOLR-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504153#comment-13504153
]
Commit Tag Bot commented on SOLR-2045:
--
[trunk commit] James Dyer
[
https://issues.apache.org/jira/browse/LUCENE-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504154#comment-13504154
]
Commit Tag Bot commented on LUCENE-3441:
[trunk commit] Shai Erera
[
https://issues.apache.org/jira/browse/LUCENE-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504155#comment-13504155
]
Commit Tag Bot commented on LUCENE-3441:
[trunk commit] Shai Erera
[
https://issues.apache.org/jira/browse/LUCENE-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504158#comment-13504158
]
Stefan Pohl commented on LUCENE-4571:
-
Mikhail, Robert, thank you for following up on
I took a look at the local repo with a git client and it seemed to show local
changes in an HTMLStripCharFilter…odd…
Anyway, I discarded those changes and let the bot run again and it caught up
with the missed tags.
Not sure if it will happen again or not (this stuff is pretty isolated and
[
https://issues.apache.org/jira/browse/LUCENE-4573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved LUCENE-4573.
--
Resolution: Fixed
Fix Version/s: 5.0
Assignee: David Smiley
Improve
[
https://issues.apache.org/jira/browse/SOLR-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504170#comment-13504170
]
Shawn Heisey commented on SOLR-4048:
The javadoc for this new method probably should
[
https://issues.apache.org/jira/browse/LUCENE-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504180#comment-13504180
]
Robert Muir commented on LUCENE-4571:
-
I like the ideas Stefan!
{quote}
Using
[
https://issues.apache.org/jira/browse/SOLR-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504181#comment-13504181
]
Shawn Heisey commented on SOLR-3948:
I tried this patch against a trunk checkout today
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer updated SOLR-2141:
-
Attachment: SOLR-2141.patch
better patch. fixes problem for SOLR-3842 also.
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer updated SOLR-2141:
-
Attachment: SOLR-2141.patch
this 3rd patch version contains a test that won't begin to fail on Jan 1 :)
[
https://issues.apache.org/jira/browse/SOLR-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-3960:
---
Attachment: SOLR-3960.patch
grouping and postfilters are two areas of internals that i'm not really
familiar
[
https://issues.apache.org/jira/browse/SOLR-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-3960:
---
Attachment: SOLR-3960.patch
slight test improvement to exercise distributed grouping both with a regular
[
https://issues.apache.org/jira/browse/SOLR-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man reassigned SOLR-3960:
--
Assignee: Hoss Man
Searching: PostFilter plugins ignored by solr cloud for queries with grouping
By the way David, I saw your last commit did not trigger a tag - looks because
you used LUCENE-XXX without a colon after it. Currently it keys on that. I can
look at making it a little more forgiving.
- Mark
On Nov 26, 2012, at 4:51 PM, Mark Miller markrmil...@gmail.com wrote:
I took a look
[
https://issues.apache.org/jira/browse/SOLR-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504276#comment-13504276
]
Hoss Man commented on SOLR-3926:
Eirik:
Thanks for bring this up and working on improving
[
https://issues.apache.org/jira/browse/SOLR-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504279#comment-13504279
]
Deniz Durmus commented on SOLR-4112:
As a feedback, would like to say that the patch
Deniz Durmus created SOLR-4113:
--
Summary: Fullpath for db-config file causes error on SolrCloud
Key: SOLR-4113
URL: https://issues.apache.org/jira/browse/SOLR-4113
Project: Solr
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SOLR-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504303#comment-13504303
]
Yonik Seeley commented on SOLR-3926:
bq. Lastly: I'm really not a fan of having
[
https://issues.apache.org/jira/browse/SOLR-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504305#comment-13504305
]
Yonik Seeley commented on SOLR-2592:
OK, fixed the bugs:
[
https://issues.apache.org/jira/browse/SOLR-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504311#comment-13504311
]
Yonik Seeley commented on SOLR-3960:
Looks good Hoss!
Searching:
[
https://issues.apache.org/jira/browse/SOLR-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504325#comment-13504325
]
Commit Tag Bot commented on SOLR-3960:
--
[trunk commit] Chris M. Hostetter
[
https://issues.apache.org/jira/browse/SOLR-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-3960.
Resolution: Fixed
Fix Version/s: 5.0
4.1
Thanks for hte review yonik, and thanks
[
https://issues.apache.org/jira/browse/SOLR-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504342#comment-13504342
]
Commit Tag Bot commented on SOLR-3960:
--
[branch_4x commit] Chris M. Hostetter
Per - keep contributing. Your contributions so far have not gone unnoticed
- you've been spotted. At least from here in New York. :)
Otis
--
SOLR Performance Monitoring - http://sematext.com/spm/index.html
Search Analytics - http://sematext.com/search-analytics/index.html
On Mon, Nov 26,
82 matches
Mail list logo
