subject:"\[jira\] \[Commented\] \(SOLR\-5103\) Plugin Improvements"


[ 
https://issues.apache.org/jira/browse/SOLR-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14702902#comment-14702902
 ] 

Jan Høydahl commented on SOLR-5103:
---

The issue description is quite describing, isn't it? We're on-topic here as far 
as I can tell:
{quote}
I think for 5.0, we should make it easier to add plugins by defining a plugin 
package, ala a Hadoop Job jar, which is a self--contained archive of a plugin 
that can be easily installed (even from the UI!) and configured 
programmatically.
{quote}
Solr's plugins today are really just Java classes that happen to implement a 
certain interface that we have defined as a plugin, and then it is up to the 
user to get hold of the plugin from somewhere, find a way to place it on the 
classpath, register the full class name into appropriate config file (varies 
depending on what the plugin does), restart Solr and then start using it.

This JIRA is trying to define a broader pluging definition, where the Java 
class is just part of it all, where dependency jars and configuration could be 
packaged with the plugin, where the whole fetch-install-configure complexity is 
hidden and can be done by the click of a GUI button or running of one shell 
command.

Besides - how many Solr plugins do you know of today in the wild? How do 
you find them? Most are just patches in JIRA, others have their own installers, 
yet others include some description of how to copy thing into various places, 
editing some XML files etc. The 3rd party market for cool new features will 
probably take off once we can offer such a simplified plugin architecture. And 
we won't force anyone, you can still plug classes in the manual way if you like.

 Plugin Improvements
 ---

 Key: SOLR-5103
 URL: https://issues.apache.org/jira/browse/SOLR-5103
 Project: Solr
  Issue Type: Improvement
Reporter: Grant Ingersoll
Assignee: Grant Ingersoll
 Fix For: Trunk


 I think for 5.0, we should make it easier to add plugins by defining a plugin 
 package, ala a Hadoop Job jar, which is a self--contained archive of a plugin 
 that can be easily installed (even from the UI!) and configured 
 programmatically.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (SOLR-5103) Plugin Improvements


[ 
https://issues.apache.org/jira/browse/SOLR-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14702947#comment-14702947
 ] 

Alexandre Rafalovitch commented on SOLR-5103:
-

I think that's a little more to a plugin than upload mechanics. There is a need 
for meta-data convention, dependency handling, versioning, etc. Supplementary 
UI.

So, making upload mechanics could be a good first step, but the bigger picture 
needs to be kept in mind as well.

BTW, Velocity loader apparently can load pages from the classpath. So, it might 
be possible to bundle pages with the plugin somehow already, if the classpath 
is setup right.

 Plugin Improvements
 ---

 Key: SOLR-5103
 URL: https://issues.apache.org/jira/browse/SOLR-5103
 Project: Solr
  Issue Type: Improvement
Reporter: Grant Ingersoll
Assignee: Grant Ingersoll
 Fix For: Trunk


 I think for 5.0, we should make it easier to add plugins by defining a plugin 
 package, ala a Hadoop Job jar, which is a self--contained archive of a plugin 
 that can be easily installed (even from the UI!) and configured 
 programmatically.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (SOLR-5103) Plugin Improvements

[
https://issues.apache.org/jira/browse/SOLR-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14702985#comment-14702985
]

Jan Høydahl commented on SOLR-5103:
---

bq. I think that's a little more to a plugin than upload mechanics. There is a
need for meta-data convention, dependency handling, versioning, etc.
Supplementary UI.

Totally agree. But we need to start in one end. Perhaps defining the minimum
zip/jar layout for what to constitute a plugin. What if we choose our own file
ending, e.g. {.solrplugin} which is really just a zip file. Then a possible
layout could be
{noformat}
my-plugin.solrplugin
/solrplugin.properties -- defining e.g. name, version, dependencies etc
/lib/ (jars to be added to classpath)
/config/config-api-commands.json (a series of commands to be run towards
config API)
/config/schema-api-commands.json (a series of commands to be run towards
config API)
{noformat}

Then, over time, we can evolve the spec and add support for pluggable UI etc.

There are tons of questions to address too
* Size limitation in blob store?
* Should Solr unpack all libs from the {{.solrplugin}} pkg and add them
individually to blob store, or write a classloader that adds everything
directly from the zip?
* What about version clash of dependencies - should not jeopardize the rest of
the system
* Should all plugins be system-level, and then require a new
{{/collection/config install-plugin}} command to enable it for each
collection?
* What about system-level plugins, such as Authentication and Authorization
plugins? Should {{security.json}} be auto updated when installing an auth
plugin, or only if it does not exist already?
* There should be a way to install plugins without registering the component
with APIs, e.g. {{bin/solr installplugin solrcell -noregister}}
* Uninstall of a plugin - it should also be able to unregister things from
config / schema, for all collections where it is enabled (scary)

First step is to see if there is enough committer interest in going down this
path, then split things up into many smaller tasks that can be handled
separately.

Plugin Improvements
---

Key: SOLR-5103
URL: https://issues.apache.org/jira/browse/SOLR-5103
Project: Solr
Issue Type: Improvement
Reporter: Grant Ingersoll
Assignee: Grant Ingersoll
Fix For: Trunk

I think for 5.0, we should make it easier to add plugins by defining a plugin
package, ala a Hadoop Job jar, which is a self--contained archive of a plugin
that can be easily installed (even from the UI!) and configured
programmatically.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (SOLR-5103) Plugin Improvements


[ 
https://issues.apache.org/jira/browse/SOLR-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703009#comment-14703009
 ] 

Noble Paul commented on SOLR-5103:
--

If someone wants to offer a plugin with dependency jars , please make a jar 
with all the dependencies included. Once you make that assumption everything 
else becomes simpler.

Then it is still possible to write a script which runs as follows

{noformat}
/bin/solr install-plugin xyz.jar -conf xyz.json -c collection1
{noformat}

or we can package the xyz.jar in such a way that the META-INF contains 
{{plugin.json}} and the command can be simplified to
{noformat}
/bin/solr install-plugin xyz.jar -c collection1
{noformat}

bq.Size limitation in blob store?

as of now it is set to 5MB by default . However the user can increase it to any 
number with a command


 Plugin Improvements
 ---

 Key: SOLR-5103
 URL: https://issues.apache.org/jira/browse/SOLR-5103
 Project: Solr
  Issue Type: Improvement
Reporter: Grant Ingersoll
Assignee: Grant Ingersoll
 Fix For: Trunk


 I think for 5.0, we should make it easier to add plugins by defining a plugin 
 package, ala a Hadoop Job jar, which is a self--contained archive of a plugin 
 that can be easily installed (even from the UI!) and configured 
 programmatically.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (SOLR-5103) Plugin Improvements


[ 
https://issues.apache.org/jira/browse/SOLR-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14702871#comment-14702871
 ] 

Noble Paul commented on SOLR-5103:
--

I fail to see what are you trying to solve here. Please give the problem 
statement and state the proposed solution. I guess it is worth opening a new 
ticket

 Plugin Improvements
 ---

 Key: SOLR-5103
 URL: https://issues.apache.org/jira/browse/SOLR-5103
 Project: Solr
  Issue Type: Improvement
Reporter: Grant Ingersoll
Assignee: Grant Ingersoll
 Fix For: Trunk


 I think for 5.0, we should make it easier to add plugins by defining a plugin 
 package, ala a Hadoop Job jar, which is a self--contained archive of a plugin 
 that can be easily installed (even from the UI!) and configured 
 programmatically.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (SOLR-5103) Plugin Improvements


[ 
https://issues.apache.org/jira/browse/SOLR-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14702953#comment-14702953
 ] 

Noble Paul commented on SOLR-5103:
--

We don't yet have a concept of a plugin offering a UI . 


 Plugin Improvements
 ---

 Key: SOLR-5103
 URL: https://issues.apache.org/jira/browse/SOLR-5103
 Project: Solr
  Issue Type: Improvement
Reporter: Grant Ingersoll
Assignee: Grant Ingersoll
 Fix For: Trunk


 I think for 5.0, we should make it easier to add plugins by defining a plugin 
 package, ala a Hadoop Job jar, which is a self--contained archive of a plugin 
 that can be easily installed (even from the UI!) and configured 
 programmatically.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (SOLR-5103) Plugin Improvements


[ 
https://issues.apache.org/jira/browse/SOLR-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703017#comment-14703017
 ] 

Jan Høydahl commented on SOLR-5103:
---

bq. If someone wants to offer a plugin with dependency jars , please make a jar 
with all the dependencies included.
Well that is for us to dictate, isn't it? Who says the plugin format must 
conform to the JAR specs? Is it technically problematic to add all classes from 
multiple JARs from within a ZIP to a classloader? If yes, the user-facing 
plugin format could still be a zip with multiple jars in a lib folder, and our 
plugin installer code handles merging all jars together into one jar 
{{plugin-xyz-merged.jar}} which is the one being registered with the 
classloader?

 Plugin Improvements
 ---

 Key: SOLR-5103
 URL: https://issues.apache.org/jira/browse/SOLR-5103
 Project: Solr
  Issue Type: Improvement
Reporter: Grant Ingersoll
Assignee: Grant Ingersoll
 Fix For: Trunk


 I think for 5.0, we should make it easier to add plugins by defining a plugin 
 package, ala a Hadoop Job jar, which is a self--contained archive of a plugin 
 that can be easily installed (even from the UI!) and configured 
 programmatically.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (SOLR-5103) Plugin Improvements


[ 
https://issues.apache.org/jira/browse/SOLR-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703072#comment-14703072
 ] 

Alexandre Rafalovitch commented on SOLR-5103:
-

Only the classloader leakage hell! :=(

There is no standard mechanism for inlining the dependencies, though there are 
a couple of different approaches, all doing weird and less than wonderful 
things with classloader mechanisms. Something like 
http://maven.apache.org/plugins/maven-shade-plugin/ and 
http://docs.spring.io/spring-boot/docs/1.3.0.BUILD-SNAPSHOT/reference/htmlsingle/#executable-jar

Or, of course, OSGI 
http://www.javaworld.com/article/2075836/description-of-osgi-layer.html

 Plugin Improvements
 ---

 Key: SOLR-5103
 URL: https://issues.apache.org/jira/browse/SOLR-5103
 Project: Solr
  Issue Type: Improvement
Reporter: Grant Ingersoll
Assignee: Grant Ingersoll
 Fix For: Trunk


 I think for 5.0, we should make it easier to add plugins by defining a plugin 
 package, ala a Hadoop Job jar, which is a self--contained archive of a plugin 
 that can be easily installed (even from the UI!) and configured 
 programmatically.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (SOLR-5103) Plugin Improvements


[ 
https://issues.apache.org/jira/browse/SOLR-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14702972#comment-14702972
 ] 

Alexandre Rafalovitch commented on SOLR-5103:
-

Actually, *wt=velocityv.template.x* allow to serve a velocity template around 
the search results. Unless broken by recent changes, etc. [~ehatcher] may be 
able to add details. 

And, if admin-extra was loaded from classpath, there might be a way to wire it 
in into UI automatically.

It may not be pretty on the first round, but at least something like /browse 
might be more possible than expected.

 Plugin Improvements
 ---

 Key: SOLR-5103
 URL: https://issues.apache.org/jira/browse/SOLR-5103
 Project: Solr
  Issue Type: Improvement
Reporter: Grant Ingersoll
Assignee: Grant Ingersoll
 Fix For: Trunk


 I think for 5.0, we should make it easier to add plugins by defining a plugin 
 package, ala a Hadoop Job jar, which is a self--contained archive of a plugin 
 that can be easily installed (even from the UI!) and configured 
 programmatically.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (SOLR-5103) Plugin Improvements


[ 
https://issues.apache.org/jira/browse/SOLR-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14702990#comment-14702990
 ] 

Alexandre Rafalovitch commented on SOLR-5103:
-

My position is still that madness lies that way if we try to reinvent plugin 
management from scratch and that 3rd party solution may make better sense for 
that. Even if that solution is not perfect.

But, on the other hand, I don't know internals of Solr well enough to know 
whether there is enough extensibility built-in to allow that.

 Plugin Improvements
 ---

 Key: SOLR-5103
 URL: https://issues.apache.org/jira/browse/SOLR-5103
 Project: Solr
  Issue Type: Improvement
Reporter: Grant Ingersoll
Assignee: Grant Ingersoll
 Fix For: Trunk


 I think for 5.0, we should make it easier to add plugins by defining a plugin 
 package, ala a Hadoop Job jar, which is a self--contained archive of a plugin 
 that can be easily installed (even from the UI!) and configured 
 programmatically.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (SOLR-5103) Plugin Improvements


[ 
https://issues.apache.org/jira/browse/SOLR-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703047#comment-14703047
 ] 

Noble Paul commented on SOLR-5103:
--

bq.Well that is for us to dictate, isn't it? Who says the plugin format must 
conform to the JAR specs?

It's OK for the plugin format not conform to jar specs. The payload could be a 
zip file with multiple jars. But, is it a big deal to merge multiple jars. It 
solves a problem of name collisions. What if the same FQN of a class is found 
in two jars , which one to load? 

bq. and our plugin installer code handles merging all jars together into one 
jar plugin-xyz-merged.jar 

Please don't . The plugin installer should do as little magic as possible.

 Plugin Improvements
 ---

 Key: SOLR-5103
 URL: https://issues.apache.org/jira/browse/SOLR-5103
 Project: Solr
  Issue Type: Improvement
Reporter: Grant Ingersoll
Assignee: Grant Ingersoll
 Fix For: Trunk


 I think for 5.0, we should make it easier to add plugins by defining a plugin 
 package, ala a Hadoop Job jar, which is a self--contained archive of a plugin 
 that can be easily installed (even from the UI!) and configured 
 programmatically.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (SOLR-5103) Plugin Improvements

2015-08-19 Thread Shawn Heisey (JIRA)


[ 
https://issues.apache.org/jira/browse/SOLR-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703050#comment-14703050
 ] 

Shawn Heisey commented on SOLR-5103:


bq. If someone wants to offer a plugin with dependency jars , please make a jar 
with all the dependencies included. Once you make that assumption everything 
else becomes simpler.

I worry about this idea a little bit.  Maybe I don't need to be worried.  What 
happens if a plugin project uses one of the same dependent jars as Solr, but 
packages a wildly different version than the version we package?  Are there any 
situations where that might cause a larger problem than using a little more 
memory?


 Plugin Improvements
 ---

 Key: SOLR-5103
 URL: https://issues.apache.org/jira/browse/SOLR-5103
 Project: Solr
  Issue Type: Improvement
Reporter: Grant Ingersoll
Assignee: Grant Ingersoll
 Fix For: Trunk


 I think for 5.0, we should make it easier to add plugins by defining a plugin 
 package, ala a Hadoop Job jar, which is a self--contained archive of a plugin 
 that can be easily installed (even from the UI!) and configured 
 programmatically.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (SOLR-5103) Plugin Improvements


[ 
https://issues.apache.org/jira/browse/SOLR-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14702925#comment-14702925
 ] 

Noble Paul commented on SOLR-5103:
--

I guess I'm getting what you are trying to say

Now we need to follow the following steps to register a plugin from a jar 
(using SOLR-7073)

# upload the jar to {{.system}} collection
# add the jar to collection classpath using the {{add-runtime-lib}} command
# add the component using the {{add-companent-naam}} command

So you are trying to eliminate step #3 here. Is that right ?

 Plugin Improvements
 ---

 Key: SOLR-5103
 URL: https://issues.apache.org/jira/browse/SOLR-5103
 Project: Solr
  Issue Type: Improvement
Reporter: Grant Ingersoll
Assignee: Grant Ingersoll
 Fix For: Trunk


 I think for 5.0, we should make it easier to add plugins by defining a plugin 
 package, ala a Hadoop Job jar, which is a self--contained archive of a plugin 
 that can be easily installed (even from the UI!) and configured 
 programmatically.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (SOLR-5103) Plugin Improvements


[ 
https://issues.apache.org/jira/browse/SOLR-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14702955#comment-14702955
 ] 

Jan Høydahl commented on SOLR-5103:
---

bq. So you are trying to eliminate step #3 here. Is that right ?
Not primarily. Your list is over simplified. Today:
# Realize that there is a plugin for what you want to do
# Locate and download that plugin
# Read the docs and find and download any dependencies of the plugin
#* Example: dist/solr-cell-5.0.0.jar is the plugin, and you also have 34 
dependency jars from contrib/lib/
# For each jar required (35 in total):
#* {{curl -X POST -H 'Content-Type: application/octet-stream' --data-binary 
@filename.jar http://localhost:8983/solr/.system/blob/name }}
# For each collection in the system (that needs the plugin):
#* For each jar that belongs to the plugin:
#** Put each jar on the classpath for the collection
#** {code}
curl http://localhost:8983/solr/collection1/config -H 
'Content-type:application/json'  -d '{
add-runtimelib : {name: jarname , version:2 },
update-runtimelib :{name: jarname ,version:3},
delete-runtimelib :jarname 
}' 
{code}
#** Register the plugin into config or schema or zookeeper or solr.xml 
depending on the type, e.g.
#** {code}
{add-searchcomponent:
   name:elevator,
   class:QueryElevationComponent,
   queryFieldType:string,
   config-file:elevate.xml
}
{code}

Not to mention when you want to upgrade the plugin to a newer version, or 
uninstall it..

Now compare this to a click in the Admin UI or:

{noformat}
bin/solr installplugin solrcell 5.2.1
bin/solr removeplugin solrcell
bin/solr installplugin solrcell 5.3.0
{noformat}

 Plugin Improvements
 ---

 Key: SOLR-5103
 URL: https://issues.apache.org/jira/browse/SOLR-5103
 Project: Solr
  Issue Type: Improvement
Reporter: Grant Ingersoll
Assignee: Grant Ingersoll
 Fix For: Trunk


 I think for 5.0, we should make it easier to add plugins by defining a plugin 
 package, ala a Hadoop Job jar, which is a self--contained archive of a plugin 
 that can be easily installed (even from the UI!) and configured 
 programmatically.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (SOLR-5103) Plugin Improvements

2015-08-19 Thread Erik Hatcher (JIRA)

[
https://issues.apache.org/jira/browse/SOLR-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703087#comment-14703087
]

Erik Hatcher commented on SOLR-5103:

bq. Actually, wt=velocityv.template.x allow to serve a velocity template
around the search results.

bq. And, if admin-extra was loaded from classpath, there might be a way to wire
it in into UI automatically. It may not be pretty on the first round, but at
least something like /browse might be more possible than expected.

VrW has a VelocitySolrResourceLoader which pulls templates (anything textual
would work), but it is constrained to only look under a `velocity/` sub-tree
from the resource loader root.

I'm not quite getting what you're getting at here though, but one can #parse
another velocity template or #include anything textual with no parsing. And
easily wrap a response with a layout to get headers/footers, etc.

Plugin Improvements
---

Key: SOLR-5103
URL: https://issues.apache.org/jira/browse/SOLR-5103
Project: Solr
Issue Type: Improvement
Reporter: Grant Ingersoll
Assignee: Grant Ingersoll
Fix For: Trunk

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (SOLR-5103) Plugin Improvements

2015-08-19 Thread Upayavira (JIRA)


[ 
https://issues.apache.org/jira/browse/SOLR-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703121#comment-14703121
 ] 

Upayavira commented on SOLR-5103:
-

All the above seems to be describing OSGi, for which we have the Apache Felix 
project here at Apache. If we are considering plugins that can hold 
conflicting dependencies, that does seem the obvious way to go.

 Plugin Improvements
 ---

 Key: SOLR-5103
 URL: https://issues.apache.org/jira/browse/SOLR-5103
 Project: Solr
  Issue Type: Improvement
Reporter: Grant Ingersoll
Assignee: Grant Ingersoll
 Fix For: Trunk


 I think for 5.0, we should make it easier to add plugins by defining a plugin 
 package, ala a Hadoop Job jar, which is a self--contained archive of a plugin 
 that can be easily installed (even from the UI!) and configured 
 programmatically.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (SOLR-5103) Plugin Improvements