lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (LUCENE-6247) artifacts are half a gigabyte
Date Mon, 16 Feb 2015 17:55:12 GMT


Robert Muir commented on LUCENE-6247:

But when people come back and say that they disagree or only comment on a part of an issue,
you are repeating exactly the same message just louder. I do not see you addressing different
impacts on developers and final users. Impact is not just size, it's historical implications,
3rd party systems, etc. 

I haven't even begun to get loud. 

I proposed specific changes to lucene, with the size impacts of each.  Maybe that is your
confusion, that this is a LUCENE issue that I opened and is quite contained to that? I don't
care about solr here, Someone else can lead the charge for solr honestly, it will not be me.
sparks are not going to fly and I am not going to develop any plugin system to deal with its
size issue.

So please, lets just comment on the very specific proposal for lucene here and not discuss
anything else irrelevant.

> artifacts are half a gigabyte
> -----------------------------
>                 Key: LUCENE-6247
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Robert Muir
>            Priority: Blocker
>             Fix For: 5.0
> This is a growing problem and now, its spun out of control.
> The latest release artifacts are half a gigabyte. sorry, I am against adding more retries
to the smoke tester and continuing down the same path (LUCENE-6231).
> Instead I open this blocker issue to discuss fixing this. Whenever i tried to fix it
before (e.g. removing zips), people complained at me "what are you trying to fix" and wouldn't
let me minimize it in the slightest.
> Now the problem is clear, we have a blocker issue to discuss it.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message