[
https://issues.apache.org/jira/browse/LUCENE-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862499#comment-13862499
]
Shai Erera commented on LUCENE-5339:
Thanks Mike! Do we need to delete the branch?
>
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/1190/
Java: 64bit/jdk1.7.0 -XX:+UseCompressedOops -XX:+UseParallelGC
All tests passed
Build Log:
[...truncated 10021 lines...]
[junit4] JVM J0: stderr was not empty, see:
/Users/jenkins/workspace/Lucene-Solr-trunk-MacOSX/solr/buil
[
https://issues.apache.org/jira/browse/SOLR-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862486#comment-13862486
]
Kranti Parisa commented on SOLR-5507:
-
+1 for plugin/component capabilities. That would
[
https://issues.apache.org/jira/browse/LUCENE-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated LUCENE-5383:
---
Attachment: LUCENE-5383.patch
patch to autolinkify text of the form "[ github | gh ] pull request [
[
https://issues.apache.org/jira/browse/LUCENE-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862460#comment-13862460
]
Hoss Man commented on LUCENE-5383:
--
bq. Don't overengineer it: your overengineered schem
Jan Høydahl created SOLR-5606:
-
Summary: REST based Collections API
Key: SOLR-5606
URL: https://issues.apache.org/jira/browse/SOLR-5606
Project: Solr
Issue Type: Improvement
Components:
OK I think I found the 2nd copy that the maven build uses ... I
committed a [hopefully correct] fix.
Mike McCandless
http://blog.mikemccandless.com
On Sat, Jan 4, 2014 at 7:20 PM, Michael McCandless
wrote:
> Hmm, I had added an exemption for this in lucene/facet/build.xml.
> Does the maven bui
[
https://issues.apache.org/jira/browse/LUCENE-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862453#comment-13862453
]
ASF subversion and git services commented on LUCENE-5339:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862452#comment-13862452
]
ASF subversion and git services commented on LUCENE-5339:
-
Commit
Hmm, I had added an exemption for this in lucene/facet/build.xml.
Does the maven build have its own copy of the exemptions?
Mike McCandless
http://blog.mikemccandless.com
On Sat, Jan 4, 2014 at 6:50 PM, Steve Rowe wrote:
> Forbidden API errors:
>
> [mvn] [INFO]
>
[
https://issues.apache.org/jira/browse/LUCENE-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-5345.
Resolution: Fixed
This was fixed with LUCENE-5339.
> range facets don't work with
Forbidden API errors:
[mvn] [INFO]
[mvn] [INFO] Building Lucene Facets
[mvn] [INFO]task-segment: [install]
[mvn] [INFO]
[...
[
https://issues.apache.org/jira/browse/SOLR-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862444#comment-13862444
]
Jan Høydahl commented on SOLR-4783:
---
Any news regarding cloud and rollback?
> Rollback
Build: https://builds.apache.org/job/Lucene-Solr-Maven-4.x/553/
All tests passed
Build Log:
[...truncated 3 lines...]
BUILD FAILED
/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-Maven-4.x/build.xml:482:
The following error occurred while executing this line:
/usr/home/hudson/hudson-slav
[
https://issues.apache.org/jira/browse/SOLR-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein resolved SOLR-5536.
--
Resolution: Fixed
> Add ValueSource collapse criteria to CollapsingQParsingPlugin
>
On Sat, Jan 4, 2014 at 4:13 PM, Jan Høydahl wrote:
>
> Sure, it's just another channel for contributions. We can still work with
> patch files in JIRA. There may be a few git steps (remote add, fetch,
> checkout) to pull down the remote code which takes some time getting used to,
> but all this
> This actually might be considered a detriment. Let's say that you're
> someplace you can review a change but not apply it. So you review it
> and determine that it's good. Then the patch creator changes it in a
> way that you don't find acceptable, but still passes all the tests.
When merging
[
https://issues.apache.org/jira/browse/LUCENE-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862417#comment-13862417
]
Steve Rowe commented on LUCENE-5383:
{quote}
bq. I would suggest a convention of "git
[
https://issues.apache.org/jira/browse/SOLR-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862411#comment-13862411
]
Shawn Heisey commented on SOLR-5604:
Thinking out loud: I hate to join a mailing list j
[
https://issues.apache.org/jira/browse/LUCENE-5361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand reassigned LUCENE-5361:
Assignee: Adrien Grand
> FVH throws away some boosts
> ---
>
>
[
https://issues.apache.org/jira/browse/SOLR-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey updated SOLR-5604:
---
Attachment: SOLR-5604-4x-just-lucene.patch
This is a patch against 4x that only makes changes in the H
[
https://issues.apache.org/jira/browse/LUCENE-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862403#comment-13862403
]
Robert Muir commented on LUCENE-5383:
-
Don't overengineer it: your overengineered sch
On Sat, Jan 4, 2014 at 1:25 PM, Shawn Heisey wrote:
> Of course, a smart committer won't ever push anything without a
> comprehensive final review, but everyone has times when they are in a
> rush to get things done.
>
> I'm wondering if my +1 might have been a little hasty. :)
>
But us acceptin
[
https://issues.apache.org/jira/browse/SOLR-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862393#comment-13862393
]
Yago Riveiro edited comment on SOLR-5507 at 1/4/14 7:39 PM:
+1
[
https://issues.apache.org/jira/browse/SOLR-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862393#comment-13862393
]
Yago Riveiro edited comment on SOLR-5507 at 1/4/14 7:39 PM:
+1
[
https://issues.apache.org/jira/browse/SOLR-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862393#comment-13862393
]
Yago Riveiro commented on SOLR-5507:
+1 for use bootstrap.
With a UI tool library with
I'm pretty sure pull requests close over the current branch revision, so
there's no way to post ipso facto modify them from the sender's perspective.
Michael Della Bitta
Applications Developer
o: +1 646 532 3062 | c: +1 917 477 7906
appinions inc.
“The Science of Influence Marketing”
18 East
On 1/4/2014 9:23 AM, Jan Høydahl wrote:
> Another beauty of PRs (at least at GitHub) is that the contributor can
> continue improving the fix in his branch through small incremental
> commits, and this will be included in the pull without the need for
> another PR.
This actually might be considere
[
https://issues.apache.org/jira/browse/SOLR-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862378#comment-13862378
]
Shawn Heisey commented on SOLR-5604:
My current thought, and I don't know whether it's
[
https://issues.apache.org/jira/browse/SOLR-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862376#comment-13862376
]
Shawn Heisey commented on SOLR-5604:
It's starting to look like the entire approach we
[
https://issues.apache.org/jira/browse/LUCENE-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862375#comment-13862375
]
Hoss Man commented on LUCENE-5383:
--
I read the whole sentence, but i only felt the need
: Who is "zarni"? This person is not related tot he issue (owned by Koji) and
has no metadata on JIRA at all.
Joji opened the issue, zarni attached the patch later (You need view "All"
on the issue, or click to the "Manage Attachments" screen -- there was no
comment posted when the patch was a
[
https://issues.apache.org/jira/browse/SOLR-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862367#comment-13862367
]
Shawn Heisey commented on SOLR-5604:
I made an attempt at a start and ran into problems
[
https://issues.apache.org/jira/browse/LUCENE-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862364#comment-13862364
]
Robert Muir commented on LUCENE-5383:
-
Don't clip my sentence in half, read the whole
Who is "zarni"? This person is not related tot he issue (owned by Koji) and has
no metadata on JIRA at all.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Chris Hostetter [mailto:hossman_luc...@fucit.o
[
https://issues.apache.org/jira/browse/LUCENE-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862363#comment-13862363
]
Hoss Man commented on LUCENE-5383:
--
bq. it should also be recognized by github so the co
I recognize that part of what happened here was a test of commiting
a patch that came from a github pull request, and seeing how the commit
affected the pull request metadata in github ... but ...
Since there actually *is* a jira for this, and since the patch submitted
via github appears to be
[
https://issues.apache.org/jira/browse/LUCENE-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862361#comment-13862361
]
Robert Muir commented on LUCENE-5383:
-
{quote}
I would suggest a convention of "githu
[
https://issues.apache.org/jira/browse/LUCENE-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862352#comment-13862352
]
Hoss Man commented on LUCENE-5383:
--
"pull request" is vague - github is the flavor of th
Hi,
> * comments on pull requests dont go to the dev@ list. i'm not happy about
> this. maybe we can somehow auto-subscribe it?
I opened https://issues.apache.org/jira/browse/INFRA-7157 about this.
Uwe
-
To unsubscribe, e-mail
I investigated about the closing:
other projects just ask the contributor to close the pull request, e.g.
"After the code has been included into the ASF codebase, you need to
close the pull request because we can't do that..."
http://camel.apache.org/contributing.html
On Sat, Jan 4, 2014 at 11:
Build: builds.flonkings.com/job/Lucene-4x-Linux-Java6-64-test-only/9163/
1 tests failed.
REGRESSION:
org.apache.lucene.index.TestIndexWriterWithThreads.testRollbackAndCommitWithThreads
Error Message:
Captured an uncaught exception in thread: Thread[id=397, name=Thread-332,
state=RUNNABLE, grou
Some things work well, some things do not.
Things that work:
* when pull request is opened, it goes to the dev@ list
* when committed to svn, its referenced correctly in the pull request
via the github mirror.
Things that dont work:
* comments on pull requests dont go to the dev@ list. i'm not ha
Thanks for testing this out!
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: rm...@apache.org [mailto:rm...@apache.org]
> Sent: Saturday, January 04, 2014 5:44 PM
> To: comm...@lucene.apache.org
> Subject
[
https://issues.apache.org/jira/browse/LUCENE-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862346#comment-13862346
]
Uwe Schindler commented on LUCENE-5383:
---
I don't trust GITHUB and the persistence o
On Sat, Jan 4, 2014 at 11:27 AM, Michael Della Bitta
wrote:
>> But keep in mind you are talking about github-type features. Moving to git
>> won't give us your compelling workflow here
>
> I don't see much reason to go through the trouble of migrating to git and
> not use Github/Bitbucket/Gerrit o
On Fri, Jan 3, 2014 at 10:32 PM, Otis Gospodnetic <
otis.gospodne...@gmail.com> wrote:
> 2 Qs from a Git noob:
> * PRs are a *Github* thing, not a Git thing, right?
>
Yes, or some Github workalike, of which there are many.
> * Don't PRs suffer from the same problem as patches in JIRA - if nobod
Thanks Michael: it seems to work fine. Ill commit your change.
Then we can discuss the bugs in the process (i see a few already, but
so far they have nothing to do with whether committers use git or svn
though)
On Sat, Jan 4, 2014 at 11:26 AM, Michael Della Bitta
wrote:
>> So from your perspecti
Robert Muir created LUCENE-5383:
---
Summary: fix changes2html to link pull requests
Key: LUCENE-5383
URL: https://issues.apache.org/jira/browse/LUCENE-5383
Project: Lucene - Core
Issue Type: Impr
> But keep in mind you are talking about github-type features. Moving to
git won't give us your compelling workflow here
I don't see much reason to go through the trouble of migrating to git and
not use Github/Bitbucket/Gerrit or something like that. At work, I'm
getting us over to Bitbucket chief
> So from your perspective, this workflow can already work today. (do
you want to try it, for some trivial fix?)
Just published a pull request. Let me know if that showed up. Ironically,
Github had a "ProTip" about using git merge --no-ff at the top. :)
Michael Della Bitta
Applications Developer
It took some getting used to GIT for me too (and I've been around since the rcs
days :)
But now I constantly prefer git over svn, and switching to git is a clear trend
among our customers too.
> * PRs are a *Github* thing, not a Git thing, right?
Yea, GitHub makes it really easy and visual. But
GitHub user mdellabitta opened a pull request:
https://github.com/apache/lucene-solr/pull/11
change the default of hl.phraseLimit to 5000 per SOLR-2794.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mdellabitta/lucene-solr trun
[
https://issues.apache.org/jira/browse/LUCENE-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-5379.
-
Resolution: Fixed
Fix Version/s: 4.7
5.0
> Kurdish Analyzer
>
[
https://issues.apache.org/jira/browse/LUCENE-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862335#comment-13862335
]
ASF subversion and git services commented on LUCENE-5379:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862334#comment-13862334
]
ASF subversion and git services commented on LUCENE-5379:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862324#comment-13862324
]
Jan Høydahl commented on SOLR-3085:
---
As it seems there is no silver bullet for all kind o
[
https://issues.apache.org/jira/browse/LUCENE-5371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-5371.
Resolution: Fixed
> Range faceting should use O(log(N)) search per hit
> -
[
https://issues.apache.org/jira/browse/LUCENE-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862292#comment-13862292
]
ASF subversion and git services commented on LUCENE-5339:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862291#comment-13862291
]
ASF subversion and git services commented on LUCENE-5371:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-5339.
Resolution: Fixed
Fix Version/s: 4.7
5.0
> Simplify the
> you see. If someone properly specifies -u while pushes a branch, it
> warns about "local changes" - 'Your branch is ahead of' about 'local
> changes'.
>
> I mean, technically there is no problem to provide toolset, which enforces a
> necessary workflow like https://twitter.com/sstephenson/st
[
https://issues.apache.org/jira/browse/LUCENE-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862289#comment-13862289
]
ASF subversion and git services commented on LUCENE-5376:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862273#comment-13862273
]
wolfgang hoschek commented on SOLR-5584:
As mentioned above, morphlines was designe
[
https://issues.apache.org/jira/browse/SOLR-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862272#comment-13862272
]
wolfgang hoschek edited comment on SOLR-5605 at 1/4/14 11:42 AM:
[
https://issues.apache.org/jira/browse/SOLR-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862272#comment-13862272
]
wolfgang hoschek commented on SOLR-5605:
Thanks for getting to the bottom of this!
[
https://issues.apache.org/jira/browse/LUCENE-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862269#comment-13862269
]
ASF subversion and git services commented on LUCENE-5339:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862268#comment-13862268
]
ASF subversion and git services commented on LUCENE-5371:
-
Commit
Robert,
Can you check my fork?
$ git clone g...@github.com:mkhludnev/bogus.git
Cloning into 'bogus'...
remote: Counting objects: 5, done.
remote: Compressing objects: 100% (2/2), done.
remote: Total 5 (delta 1), reused 5 (delta 1)
Receiving objects: 100% (5/5), done.
Resolving deltas: 100% (1/1),
[
https://issues.apache.org/jira/browse/SOLR-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862242#comment-13862242
]
Upayavira commented on SOLR-5507:
-
i.e. allow some of the JS etc to be defined in solrconfi
70 matches
Mail list logo
