[jira] [Commented] (SOLR-5507) Admin UI - Refactoring using AngularJS

[ https://issues.apache.org/jira/browse/SOLR-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862230#comment-13862230 ] Otis Gospodnetic commented on SOLR-5507: {quote} One of the things I would really l

Re: The Old Git Discussion

> > Also: if you fork https://github.com/apache/lucene-solr today, you can > have this workflow, I think. > This is how I worked on several Lucene issues in parallel, so it works .. sort of. The problem is that while your github changes are public, none of this appears in the Apache SVN after I co

[jira] [Commented] (SOLR-5605) MapReduceIndexerTool fails in some locales -- seen in random failures of MapReduceIndexerToolArgumentParserTest

[ https://issues.apache.org/jira/browse/SOLR-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862220#comment-13862220 ] Hoss Man commented on SOLR-5605: Filling this because i encountered it in randomized testin

[jira] [Created] (SOLR-5605) MapReduceIndexerTool fails in some locales -- seen in random failures of MapReduceIndexerToolArgumentParserTest

Hoss Man created SOLR-5605: -- Summary: MapReduceIndexerTool fails in some locales -- seen in random failures of MapReduceIndexerToolArgumentParserTest Key: SOLR-5605 URL: https://issues.apache.org/jira/browse/SOLR-5605

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

Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/1069/ 1 tests failed. REGRESSION: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.testDistribSearch Error Message: null Stack Trace: java.lang.AssertionError: null at __randomizedtesting.SeedInfo.seed([917E9FCE720E4AD4

Re: The Old Git Discussion

Hi, On Fri, Jan 3, 2014 at 2:42 PM, Michael Della Bitta < michael.della.bi...@appinions.com> wrote: > > On Fri, Jan 3, 2014 at 2:03 PM, Erick Erickson wrote: > >> If someone could outline, in concrete terms, the workflow that would make >> Git help make my life easier, or outline why staying with

[jira] [Updated] (SOLR-5463) Provide cursor/token based "searchAfter" support that works with arbitrary sorting (ie: "deep paging")

[ https://issues.apache.org/jira/browse/SOLR-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man updated SOLR-5463: --- Attachment: SOLR-5463.patch New in this patch... * user error if trying to use cursor with grouping ** I actu

[jira] [Commented] (LUCENE-2228) AES Encrypted Directory

[ https://issues.apache.org/jira/browse/LUCENE-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861923#comment-13861923 ] Peter Karich commented on LUCENE-2228: -- What is the state here? > AES Encrypted Dir

Re: The Old Git Discussion

On Fri, Jan 3, 2014 at 2:42 PM, Michael Della Bitta wrote: > That's a *lot* less compelling to me than the ability of creating my own > branch in a public arena, possibly collaborating with another person on a > change, and then issuing a pull request. Plus, there's a public record of > the work,

Re: The Old Git Discussion

On Fri, Jan 3, 2014 at 2:42 PM, Michael Della Bitta wrote: > That's a *lot* less compelling to me than the ability of creating my own > branch in a public arena, possibly collaborating with another person on a > change, and then issuing a pull request. Plus, there's a public record of > the work,

Re: The Old Git Discussion

On Fri, Jan 3, 2014 at 2:03 PM, Erick Erickson wrote: > If someone could outline, in concrete terms, the workflow that would make > Git help make my life easier, or outline why staying with SVN is going to > slow people down or turn people off, it would be a great help I guess speaking as someon

[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-tabpanel&focusedCommentId=13861807#comment-13861807 ] ASF subversion and git services commented on SOLR-5577: --- Commit 15552

[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-tabpanel&focusedCommentId=13861794#comment-13861794 ] ASF subversion and git services commented on SOLR-5577: --- Commit 15552

[jira] [Commented] (SOLR-5604) Remove deprecations caused by httpclient 4.3.x upgrade

[ https://issues.apache.org/jira/browse/SOLR-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861788#comment-13861788 ] Shawn Heisey commented on SOLR-5604: I made the same upgrade in my SolrJ application so

Re: The Old Git Discussion

Personally, I loathe Git. Maybe it's just that I'm old school or have grown used to SVN, but every time I use Git, I get lost. Branch, merge, push, pull, clone, and pray don't screw up because you'll be in a rat-hole that has no end. "But just issue commands X, Y, Z. Followed by A, B, C. Oh, and b

Re: svn commit: r1555084 - in /lucene/dev/branches/branch_4x: ./ solr/ solr/CHANGES.txt solr/core/ solr/core/src/java/org/apache/solr/cloud/OverseerCollectionProcessor.java

This is a 4.7 feature so there is no need to backport. Thanks for noticing this bug Hoss. On Fri, Jan 3, 2014 at 9:07 PM, Chris Hostetter wrote: > > Is this a good candidate for 4.6.1? > > > : Date: Fri, 03 Jan 2014 13:41:16 - > : From: sha...@apache.org > : Reply-To: dev@lucene.apache.org >

[jira] [Created] (SOLR-5604) Remove deprecations caused by httpclient 4.3.x upgrade

Shawn Heisey created SOLR-5604: -- Summary: Remove deprecations caused by httpclient 4.3.x upgrade Key: SOLR-5604 URL: https://issues.apache.org/jira/browse/SOLR-5604 Project: Solr Issue Type: Imp

Re: The Old Git Discussion

Aha, gotcha. Thanks for elucidating. Michael Della Bitta Applications Developer o: +1 646 532 3062 | c: +1 917 477 7906 appinions inc. “The Science of Influence Marketing” 18 East 41st Street New York, NY 10017 t: @appinions | g+: plus.google.com/appinions

Re: The Old Git Discussion

On Fri, Jan 3, 2014 at 1:15 PM, Michael Della Bitta wrote: >> My working directory _IS NOT_ clean if 'git push' would do something. > > I just wanted to make sure you understand this... 'git push' operates > between your local repository and the remote repository you specify, and not > on working

Re: The Old Git Discussion

> My working directory _IS NOT_ clean if 'git push' would do something. I just wanted to make sure you understand this... 'git push' operates between your local repository and the remote repository you specify, and not on working directories, right? 'git status' comes up clean because there are no

Re: The Old Git Discussion

On Fri, Jan 3, 2014 at 12:15 PM, Dawid Weiss wrote: >> But if you just tell me "you are holding it wrong", then thats keeping that >> shitty git attitude > > Don't take it personally, Robert. I meant it to be a sincere > discussion and looking for solutions rather than aggregating flame > wars.

Re: The Old Git Discussion

> But if you just tell me "you are holding it wrong", then thats keeping that > shitty git attitude Don't take it personally, Robert. I meant it to be a sincere discussion and looking for solutions rather than aggregating flame wars. I prefer git over svn now even if I used svn for a long time (a

Re: The Old Git Discussion

I don't see it that way. I guess just due to the attitude surrounding git at least, that's enough for me to press forward with my veto. Alternatively, you could decide that the "attitude that comes with git" is not also coming here with it, and try to work with me and address my specific concerns

RE: The Old Git Discussion

It also doesn't deal with a major difference between git and svn - in svn, directories are first-class objects, and in git they aren't (they are created as needed). So when you try using gitsvn you almost always wind up with directories you want to remove but can't. Karl From: ext Michael Del

Re: JDK 1.8 failure

Let's wait and see if it ever occurs again; if it does, I'll create a proper issue. These things (GC-related issues) are virtually impossible to reproduce because of inherent races between GC and application threads (my own personal impression :). Dawid On Fri, Jan 3, 2014 at 3:04 PM, Rory O'Donn

Re: The Old Git Discussion

> Question: is it possible to keep the back-end SVN, but have people interact with it through GIT or SVN clients? My experience with GIT was by forking Lucene's GIT on github, but I never tried committing from there... There's git svn: http://git-scm.com/book/ch8-1.html But it doesn't really achi

Re: The Old Git Discussion

I tried working with git several times, every time I told myself "this time you're going to give it a serious try", and yet I kept going back to SVN each and every time. At times I thought "it's because you're too familiar with SVN, git is probably at least as good once you'll get to master it". Bu

Re: The Old Git Discussion

I personally have -0 I don't have any preference. Minus because it would change my comfortable workflow. Is there any pressing need to switch? Or, if someone has to give one real reason for the switch, what would it be ? On 3 Jan 2014 20:49, "Mark Miller" wrote: > Just to answer some of your que

Re: svn commit: r1555084 - in /lucene/dev/branches/branch_4x: ./ solr/ solr/CHANGES.txt solr/core/ solr/core/src/java/org/apache/solr/cloud/OverseerCollectionProcessor.java

Is this a good candidate for 4.6.1? : Date: Fri, 03 Jan 2014 13:41:16 - : From: sha...@apache.org : Reply-To: dev@lucene.apache.org : To: comm...@lucene.apache.org : Subject: svn commit: r1555084 - in /lucene/dev/branches/branch_4x: ./ solr/ : solr/CHANGES.txt solr/core/ : solr/core/

[jira] [Commented] (SOLR-5590) SolrJ is still on httpcomponents/httpclient version 4.2.x, which has some problems

[ https://issues.apache.org/jira/browse/SOLR-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861598#comment-13861598 ] Karl Wright commented on SOLR-5590: --- You're welcome. > SolrJ is still on httpcomponents/

[jira] [Resolved] (SOLR-5590) SolrJ is still on httpcomponents/httpclient version 4.2.x, which has some problems

[ https://issues.apache.org/jira/browse/SOLR-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Heisey resolved SOLR-5590. Resolution: Fixed > SolrJ is still on httpcomponents/httpclient version 4.2.x, which has some > pro

[jira] [Commented] (SOLR-5590) SolrJ is still on httpcomponents/httpclient version 4.2.x, which has some problems

[ https://issues.apache.org/jira/browse/SOLR-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861594#comment-13861594 ] Shawn Heisey commented on SOLR-5590: Thank you for the patch, Karl! > SolrJ is still

Re: The Old Git Discussion

Just to answer some of your questions: On Jan 3, 2014, at 8:18 AM, Uwe Schindler wrote: > Hi, > > I fully agree with Robert: I don't want to move to GIT. In addition, unless > there is some tool that works as good as Windows' TortoiseSVN also for GIT, > so I can merge in milliseconds(TM), I w

Re: The Old Git Discussion

Well, no one is calling the vote yet, but if we did, I suppose each voter would have to take the loss of your contributions into account in their vote ;) I’m not in a hurry yet. Eventually though, you lose much more bowing to the people stuck on the last decades technology than you gain IMO. Jus

RE: The Old Git Discussion

As an interested party, and deeply involved in another related Apache project, I have to say that there is a huge benefit for all Apache projects to use common source control. If we were starting over, or if svn was going to die forever, it might be a different story - but given that svn is ali

Re: JDK 1.8 failure

Hi Dawid, I am currently on vacation, please do log an incident when you are ready ? Rgds,Rory On 03/01/2014 09:31, Dawid Weiss wrote: Hi Rory, A crash with build 1.8.0-ea-b121/ 32 bit: V [libjvm.so+0x6d9411] ObjArrayKlass::oop_oop_iterate_nv(oopDesc*, ParScanWithoutBarrierClosure*)+0x61 I

[jira] [Commented] (SOLR-5601) NPE in OverseerCollectionProcessor.migrateKey - inconsistent failure from MigrateRouteKeyTest

[ https://issues.apache.org/jira/browse/SOLR-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861519#comment-13861519 ] ASF subversion and git services commented on SOLR-5601: --- Commit 15550

[jira] [Commented] (SOLR-5601) NPE in OverseerCollectionProcessor.migrateKey - inconsistent failure from MigrateRouteKeyTest

[ https://issues.apache.org/jira/browse/SOLR-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861508#comment-13861508 ] ASF subversion and git services commented on SOLR-5601: --- Commit 15550

[jira] [Comment Edited] (SOLR-5476) Overseer Role for nodes

[ https://issues.apache.org/jira/browse/SOLR-5476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861496#comment-13861496 ] Noble Paul edited comment on SOLR-5476 at 1/3/14 1:25 PM: -- added a

[jira] [Updated] (SOLR-5476) Overseer Role for nodes

[ https://issues.apache.org/jira/browse/SOLR-5476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-5476: - Attachment: SOLR-5476.patch attached a patch > Overseer Role for nodes > --- > >

[jira] [Assigned] (SOLR-5601) NPE in OverseerCollectionProcessor.migrateKey - inconsistent failure from MigrateRouteKeyTest

[ https://issues.apache.org/jira/browse/SOLR-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar reassigned SOLR-5601: --- Assignee: Shalin Shekhar Mangar > NPE in OverseerCollectionProcessor.migrateKe

[jira] [Updated] (SOLR-5601) NPE in OverseerCollectionProcessor.migrateKey - inconsistent failure from MigrateRouteKeyTest

[ https://issues.apache.org/jira/browse/SOLR-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar updated SOLR-5601: Attachment: SOLR-5601.patch This should fix it. It was possible that the temp collec

[jira] [Updated] (SOLR-5601) NPE in OverseerCollectionProcessor.migrateKey - inconsistent failure from MigrateRouteKeyTest

[ https://issues.apache.org/jira/browse/SOLR-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar updated SOLR-5601: Component/s: SolrCloud Affects Version/s: 4.7 Fix Version/s: 4.7

RE: The Old Git Discussion

Hi, I fully agree with Robert: I don't want to move to GIT. In addition, unless there is some tool that works as good as Windows' TortoiseSVN also for GIT, so I can merge in milliseconds(TM), I won't commit anything. I just note: I was working as committer for the PHP project (maintaining the

Re: The Old Git Discussion

Well, once we are ready to truly decide to move, this would be a majority vote, so based on all the previous polling done, I think we would end up using git. - Mark On Jan 3, 2014, at 6:59 AM, Dawid Weiss wrote: >> then we won't use git. > > Unless somebody can offer a workflow that you can

Re: The Old Git Discussion

> then we won't use git. Unless somebody can offer a workflow that you can live with (that satisfies your criteria)? You seem to be stuck on one particular way of doing things that doesn't work for you. Fine. But there are plenty of ways of achieving a merge, including cherry-picking, preconfiguri

Re: The Old Git Discussion

then we won't use git. On Fri, Jan 3, 2014 at 6:35 AM, Dawid Weiss wrote: > This won't be fixed, because it's not a bug. > > Dawid > > On Fri, Jan 3, 2014 at 12:27 PM, Robert Muir wrote: >> On Fri, Jan 3, 2014 at 6:16 AM, Dawid Weiss >> wrote: >> >>> >>> Anyway, I recall I gave up a long time a

[jira] [Updated] (SOLR-4089) FastVectorHighlighter produces superflouos snippets for alternateField

[ https://issues.apache.org/jira/browse/SOLR-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus Jelsma updated SOLR-4089: Attachment: (was: SOLR-4089-trunk-1.patch) > FastVectorHighlighter produces superflouos snippets

[jira] [Updated] (SOLR-4089) FastVectorHighlighter produces superflouos snippets for alternateField

[ https://issues.apache.org/jira/browse/SOLR-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus Jelsma updated SOLR-4089: Attachment: SOLR-4089-trunk.patch Proper patch for trunk. > FastVectorHighlighter produces superflo

Re: The Old Git Discussion

This won't be fixed, because it's not a bug. Dawid On Fri, Jan 3, 2014 at 12:27 PM, Robert Muir wrote: > On Fri, Jan 3, 2014 at 6:16 AM, Dawid Weiss > wrote: > >> >> Anyway, I recall I gave up a long time ago to change your opinion on >> the subject. :) >> > > I guess thats not going to happen:

[jira] [Commented] (SOLR-3583) Percentiles for facets, pivot facets, and distributed pivot facets

[ https://issues.apache.org/jira/browse/SOLR-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861449#comment-13861449 ] Fang Xu commented on SOLR-3583: --- I resolved some failures of applying SOLR-2894. The I run th

Re: The Old Git Discussion

On Fri, Jan 3, 2014 at 6:16 AM, Dawid Weiss wrote: > > Anyway, I recall I gave up a long time ago to change your opinion on > the subject. :) > I guess thats not going to happen: its not acceptable to me. If you want me to withdraw my -1, this bug actually needs to be fixed :) I know git fanati

Re: The Old Git Discussion

> My working directory _IS NOT_ clean if 'git push' would do something. I disagree. Your working directory state is defined as the identity between files in your checkout folder against the revision pointed to by your HEAD reference. And this is fulfilled. You merge from master results in a fast f

Re: The Old Git Discussion

On 01/03/2014 12:13 AM, Shawn Heisey wrote: I can't make any cogent arguments about whether git is superior to subversion at the basic job of version control, whether it produces better workflows, or any similar argument. Generally speaking, I do think it's a good idea for projects like Apache to

Re: The Old Git Discussion

On Fri, Jan 3, 2014 at 3:31 AM, Dawid Weiss wrote: >> ^^^ see that shit? it says the words 'working directory clean' but it >> lies. > > No, it doesn't lie. You are holding it wrong. > > If a merge can proceed without conflicts, it will commit > automatically, so your working copy *is* clean.

[jira] [Updated] (SOLR-5594) Enable using extended field types with prefix queries for non-default encoded strings

[ https://issues.apache.org/jira/browse/SOLR-5594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-5594: --- Attachment: SOLR-5594-branch_4x.patch Patch for 4x with test. There one thing I'd like to do better th

JDK 1.8 failure

Hi Rory, A crash with build 1.8.0-ea-b121/ 32 bit: V [libjvm.so+0x6d9411] ObjArrayKlass::oop_oop_iterate_nv(oopDesc*, ParScanWithoutBarrierClosure*)+0x61 Issue at: https://issues.apache.org/jira/browse/LUCENE-5382 We didn't have time to look at if it reproduces yet. Dawid --

Re: [JENKINS] Lucene-Solr-trunk-Linux (32bit/jdk1.8.0-ea-b121) - Build # 8929 - Failure!

I filed: https://issues.apache.org/jira/browse/LUCENE-5382 Didn't have the time to try if it reproduces (doubt it). Dawid On Thu, Jan 2, 2014 at 5:39 PM, Dawid Weiss wrote: > I don't recall seing this one before. > > D. > > On Thu, Jan 2, 2014 at 5:37 PM, Robert Muir wrote: >> this is new i t

[jira] [Commented] (SOLR-5564) hl.maxAlternateFieldLength should apply to original field when fallback field does not exist

[ https://issues.apache.org/jira/browse/SOLR-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861378#comment-13861378 ] ASF subversion and git services commented on SOLR-5564: --- Commit 15550

[jira] [Moved] (LUCENE-5382) SIGSEGV in jdk 1.8.0 ea b121 (32 bit)

[ https://issues.apache.org/jira/browse/LUCENE-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dawid Weiss moved SOLR-5603 to LUCENE-5382: --- Lucene Fields: New Key: LUCENE-5382 (was: SOLR-5603)

[jira] [Resolved] (SOLR-5564) hl.maxAlternateFieldLength should apply to original field when fallback field does not exist

[ https://issues.apache.org/jira/browse/SOLR-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl resolved SOLR-5564. --- Resolution: Fixed Committed and fixed from v4.6.1 > hl.maxAlternateFieldLength should apply to origin

[jira] [Created] (SOLR-5603) SIGSEGV in jdk 1.8.0 ea b121 (32 bit)

Dawid Weiss created SOLR-5603: - Summary: SIGSEGV in jdk 1.8.0 ea b121 (32 bit) Key: SOLR-5603 URL: https://issues.apache.org/jira/browse/SOLR-5603 Project: Solr Issue Type: Bug Report

[jira] [Updated] (SOLR-5603) SIGSEGV in jdk 1.8.0 ea b121 (32 bit)

[ https://issues.apache.org/jira/browse/SOLR-5603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dawid Weiss updated SOLR-5603: -- Attachment: hs_err_pid27661.log > SIGSEGV in jdk 1.8.0 ea b121 (32 bit) > --

[jira] [Commented] (SOLR-5564) hl.maxAlternateFieldLength should apply to original field when fallback field does not exist

[ https://issues.apache.org/jira/browse/SOLR-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861372#comment-13861372 ] ASF subversion and git services commented on SOLR-5564: --- Commit 15550

[jira] [Commented] (SOLR-5564) hl.maxAlternateFieldLength should apply to original field when fallback field does not exist

[ https://issues.apache.org/jira/browse/SOLR-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861365#comment-13861365 ] ASF subversion and git services commented on SOLR-5564: --- Commit 15550

[jira] [Commented] (SOLR-3583) Percentiles for facets, pivot facets, and distributed pivot facets

[ https://issues.apache.org/jira/browse/SOLR-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861357#comment-13861357 ] Fang Xu commented on SOLR-3583: --- Hi Terrance, I mean the patch needs SOLR-2894. SOLR-289

[jira] [Assigned] (SOLR-5564) hl.maxAlternateFieldLength should apply to original field when fallback field does not exist

[ https://issues.apache.org/jira/browse/SOLR-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl reassigned SOLR-5564: - Assignee: Jan Høydahl > hl.maxAlternateFieldLength should apply to original field when fallback fi

Re: The Old Git Discussion

+1 -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com 2. jan. 2014 kl. 21:51 skrev Mark Miller : > bzr is dying; Emacs needs to move > > > http://lists.gnu.org/archive/html/emacs-devel/2014-01/msg5.html > > Interesting thread. > > For similar reasons, I think that

[jira] [Updated] (SOLR-5598) LanguageIdentifierUpdateProcessor ignores all but the first value of multiValued string fields

[ https://issues.apache.org/jira/browse/SOLR-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-5598: -- Fix Version/s: 4.7 > LanguageIdentifierUpdateProcessor ignores all but the first value of > multiValued

Re: The Old Git Discussion

On Fri, Jan 3, 2014 at 4:13 AM, Robert Muir wrote: > It happens with 1.8 too. I'm not really concerned what the technical > explanation is (i'm sure someone will say: you are holding it wrong). > > one of the most important things about version control is being able > to track changes. if 'status

Re: The Old Git Discussion

> ^^^ see that shit? it says the words 'working directory clean' but it > lies. No, it doesn't lie. You are holding it wrong. If a merge can proceed without conflicts, it will commit automatically, so your working copy *is* clean. If you don't want to perform this final commit automatically