[jira] [Created] (SOLR-3387) UpdateRequestHandler should support XML,CSV,JSON, and javabin
UpdateRequestHandler should support XML,CSV,JSON, and javabin - Key: SOLR-3387 URL: https://issues.apache.org/jira/browse/SOLR-3387 Project: Solr Issue Type: Improvement Reporter: Ryan McKinley Fix For: 4.0 Rather then have 4 handlers to support 4 content types, we should use a single endpoint and pick the ContentStreamLoader based on the ContentType This will simplify configuration problems for clients that want to swtich format (see SOLR-3038) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3371) Admin UI breaks with a core named 'logging' or 'threads'
Admin UI breaks with a core named 'logging' or 'threads' Key: SOLR-3371 URL: https://issues.apache.org/jira/browse/SOLR-3371 Project: Solr Issue Type: Bug Reporter: Ryan McKinley Assignee: Stefan Matheis (steffkes) Fix For: 4.0 If you make a core with the name "logging" or "threads" the UI gets confused with the logging or threads page. It seems like the ~threads and ~logging should be enough to distinguish -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3368) Index Logging Events
Index Logging Events Key: SOLR-3368 URL: https://issues.apache.org/jira/browse/SOLR-3368 Project: Solr Issue Type: New Feature Reporter: Ryan McKinley In SOLR-3358, we capture logging events and hold them in memory. To support search and longer history, we could optionally store the events in a solr index -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3367) Show Logging Events in Admin UI
Show Logging Events in Admin UI --- Key: SOLR-3367 URL: https://issues.apache.org/jira/browse/SOLR-3367 Project: Solr Issue Type: New Feature Reporter: Ryan McKinley Fix For: 4.0 We can show logging events in the Admin UI. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3358) Show Logging Events in Admin UI
Show Logging Events in Admin UI --- Key: SOLR-3358 URL: https://issues.apache.org/jira/browse/SOLR-3358 Project: Solr Issue Type: Bug Components: web gui Reporter: Ryan McKinley Assignee: Ryan McKinley The UI should be able to show the last few log messages. To support this, we will need to register an Appender (log4j) or Handler (JUL) and keep a buffer of recent log events. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3356) Logging UI (and LogLevelHandler) should support Log4j
Logging UI (and LogLevelHandler) should support Log4j - Key: SOLR-3356 URL: https://issues.apache.org/jira/browse/SOLR-3356 Project: Solr Issue Type: Improvement Reporter: Ryan McKinley Assignee: Ryan McKinley Priority: Minor Fix For: 4.0 The Logging UI and LogLevelHandler can work using Log4j rather then just JUL -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3330) Show changes in plugin statistics across multiple requests
Show changes in plugin statistics across multiple requests -- Key: SOLR-3330 URL: https://issues.apache.org/jira/browse/SOLR-3330 Project: Solr Issue Type: New Feature Components: web gui Reporter: Ryan McKinley Fix For: 4.0 When debugging configuration and performance, I often: 1. Look at stats values 2. run some queries 3. See how the stats values changed This is fine, but is often a bit clunky and you have to really know what you are looking for to see any changes. It would be great if the 'plugins' page had a button that would make this easier -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3329) Use consistent svn:keywords
Use consistent svn:keywords
---
Key: SOLR-3329
URL: https://issues.apache.org/jira/browse/SOLR-3329
Project: Solr
Issue Type: Improvement
Reporter: Ryan McKinley
Fix For: 4.0
In solr, use use svn:keywords haphazardly
We have lots of places with:
{code}
svn propset svn:keywords "Date Author Id Revision HeadURL" *.java
{code}
In LUCENE-3923, there is a suggestion to get rid of many of these.
The MBeans interface often exposes HeadURL, but we likely want to get rid of
the rest
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3327) Logging UI should indicate which loggers are set vs implicit
Logging UI should indicate which loggers are set vs implicit Key: SOLR-3327 URL: https://issues.apache.org/jira/browse/SOLR-3327 Project: Solr Issue Type: Improvement Components: web gui Reporter: Ryan McKinley Priority: Trivial Fix For: 4.0 The new logging UI looks great! http://localhost:8983/solr/#/~logging It would be nice to indicate which ones are set explicitly vs implicit -- perhaps making the line bold when set=true -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3326) Convert plugin documentation links to real links
Convert plugin documentation links to real links
Key: SOLR-3326
URL: https://issues.apache.org/jira/browse/SOLR-3326
Project: Solr
Issue Type: Improvement
Components: web gui
Reporter: Ryan McKinley
Priority: Trivial
Fix For: 4.0
Right now when we show the plugin info, links are just plaintext. For:
http://localhost:8983/solr/#/singlecore/plugins/other?entry=org.apache.solr.handler.component.QueryElevationComponent
we see:
{code}
src: $URL:
https://svn.apache.org/repos/asf/lucene/dev/trunk/solr/core/src/java/org/apache/solr/handler/component/QueryElevationComponent.java
$
docs: http://wiki.apache.org/solr/QueryElevationComponent
{code}
It would be great if that actually linked to the URLS.
perhaps using something like:
https://code.google.com/p/jquery-linkifier/source/browse/jquery.gn.linkifier.js
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3325) Linking to query page in UI with parameters should execute the query
Linking to query page in UI with parameters should execute the query Key: SOLR-3325 URL: https://issues.apache.org/jira/browse/SOLR-3325 Project: Solr Issue Type: Improvement Components: web gui Reporter: Ryan McKinley Fix For: 4.0 When linking to the query page with parameters, this should execute the query. Right now linking to: http://localhost:8983/solr/#/singlecore/query?q=id:[*%20TO%20*] requires you to then hit the 'Execute Query' button -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3324) Put field name/type in the analysis URL
Put field name/type in the analysis URL Key: SOLR-3324 URL: https://issues.apache.org/jira/browse/SOLR-3324 Project: Solr Issue Type: Improvement Components: web gui Reporter: Ryan McKinley Priority: Trivial Fix For: 4.0 It would be nice to be able to link directly to a page that loads the right field in the analysis UI. This will also let us link the query-browser page to the analysis page -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3311) System Admin UI not loading memory graph
System Admin UI not loading memory graph Key: SOLR-3311 URL: https://issues.apache.org/jira/browse/SOLR-3311 Project: Solr Issue Type: Bug Components: web gui Affects Versions: 4.0 Environment: windows Reporter: Ryan McKinley Assignee: Stefan Matheis (steffkes) Priority: Minor Attachments: system.png The memory graphs on the system dashboard don't show memory useage anymore -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (LUCENE-3933) Cloneable classes can use their class in the clone() function
Cloneable classes can use their class in the clone() function
-
Key: LUCENE-3933
URL: https://issues.apache.org/jira/browse/LUCENE-3933
Project: Lucene - Java
Issue Type: Improvement
Reporter: Ryan McKinley
Assignee: Ryan McKinley
Priority: Trivial
Since Java5, we are allowed to use an explicit class when returning clone()
It is nicer to use:
{code:java}
OpenBitSet copy = original.clone();
{code}
then
{code:java}
OpenBitSet copy = (OpenBitSet)original.clone();
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3209) solrj FieldStatsInfo can not assume Double
solrj FieldStatsInfo can not assume Double -- Key: SOLR-3209 URL: https://issues.apache.org/jira/browse/SOLR-3209 Project: Solr Issue Type: Improvement Reporter: Ryan McKinley Priority: Minor Fix For: 4.0 Since SOLR-1023, the response from a stats request can be Number, Date, or even string. But FieldStatsInfo always assumes Double and will get a class cast exception. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3208) Implement Logging UI with /admin/logging handler
Implement Logging UI with /admin/logging handler Key: SOLR-3208 URL: https://issues.apache.org/jira/browse/SOLR-3208 Project: Solr Issue Type: Improvement Reporter: Ryan McKinley Fix For: 4.0 The admin UI currently uses a stub /logging.json to display a tree. It should use the LogLevelHandler -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3205) Better error reporting from Analysis UI
Better error reporting from Analysis UI
---
Key: SOLR-3205
URL: https://issues.apache.org/jira/browse/SOLR-3205
Project: Solr
Issue Type: Bug
Components: web gui
Reporter: Ryan McKinley
Fix For: 4.0
The new analysis UI does not behave well with invalid input. To reproduce,
from /#/singlecore/analysis
* Select a number field (int)
* put in invalid text (hello)
* click Analyse Values
The UI will have a red banner, but not say anything useful. The log file will
say:
{code}
SEVERE: org.apache.solr.common.SolrException: Invalid Number: hello
at
org.apache.solr.analysis.TrieTokenizer.reset(TrieTokenizerFactory.java:113)
at
org.apache.solr.analysis.TrieTokenizer.(TrieTokenizerFactory.java:76)
{code}
Hopefully we can get the UI to say "Invalid Number: hello"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3202) Remove JSP from solr webapp
Remove JSP from solr webapp --- Key: SOLR-3202 URL: https://issues.apache.org/jira/browse/SOLR-3202 Project: Solr Issue Type: Task Reporter: Ryan McKinley Assignee: Ryan McKinley Fix For: 4.0 The 4.0 admin UI does not use JSP to create its interface (It uses javascript and RequestHandlers) We only use JSP to fill in the path to the core in index.jsp -- this can be replaced with simple template text -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3174) Visualize Cluster State
Visualize Cluster State --- Key: SOLR-3174 URL: https://issues.apache.org/jira/browse/SOLR-3174 Project: Solr Issue Type: New Feature Reporter: Ryan McKinley It would be great to visualize the cluster state in the new UI. See Mark's wish: https://issues.apache.org/jira/browse/SOLR-3162?focusedCommentId=13218272&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13218272 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3159) Upgrade to Jetty 8
Upgrade to Jetty 8 -- Key: SOLR-3159 URL: https://issues.apache.org/jira/browse/SOLR-3159 Project: Solr Issue Type: Task Reporter: Ryan McKinley Priority: Minor Fix For: 4.0 Solr is currently tested (and bundled) with a patched jetty-6 version. Ideally we can release and test with a standard version. Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3155) Zookeeper info servlet should use JSON library
Zookeeper info servlet should use JSON library -- Key: SOLR-3155 URL: https://issues.apache.org/jira/browse/SOLR-3155 Project: Solr Issue Type: Improvement Reporter: Ryan McKinley Some of the JSON that the zookeeper info servlet spits out is not valid. Rather then try to fix it, I think we should just use an existing (tested!) json framework. the noggit writer is available, or maybe expose the solr JSONWriter -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3151) Replace zookeeper.jsp with a servlet
Replace zookeeper.jsp with a servlet Key: SOLR-3151 URL: https://issues.apache.org/jira/browse/SOLR-3151 Project: Solr Issue Type: Improvement Reporter: Ryan McKinley Fix For: 4.0 The zookeeper info is currently generated with a jsp file -- making it harder to maintain then it should be, and harder to include in other applications -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3134) Include shard Information in response
Include shard Information in response - Key: SOLR-3134 URL: https://issues.apache.org/jira/browse/SOLR-3134 Project: Solr Issue Type: Improvement Components: SearchComponents - other Reporter: Ryan McKinley Assignee: Ryan McKinley Fix For: 4.0 For distributed search where each shard represents a logically different index (or physical location), it would be great to know the hit count for each shard. In addition, it would be nice to get error info for each shard rather then aborting the whole request when something fails. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3121) Make new admin UI work better with big indexes
Make new admin UI work better with big indexes -- Key: SOLR-3121 URL: https://issues.apache.org/jira/browse/SOLR-3121 Project: Solr Issue Type: Improvement Affects Versions: 4.0 Reporter: Ryan McKinley Fix For: 4.0 As reported in SOLR-2667, the admin UI gets pretty bad with big indexes. Mostly this seems the fault of excessive calls to luke and not limiting the number of terms -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-2831) BinaryResponseWriter does not read/write IndexableFields correctly
BinaryResponseWriter does not read/write IndexableFields correctly -- Key: SOLR-2831 URL: https://issues.apache.org/jira/browse/SOLR-2831 Project: Solr Issue Type: Bug Reporter: Ryan McKinley When adding a SolrDocument with IndexableFields for values to a response, the values are written using toString() rather then the real value. I noticed this issue using the new RealtimeGetComponent. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-2830) RealTimeGet does not respect transformers
RealTimeGet does not respect transformers - Key: SOLR-2830 URL: https://issues.apache.org/jira/browse/SOLR-2830 Project: Solr Issue Type: Bug Reporter: Ryan McKinley Assignee: Ryan McKinley Fix For: 4.0 The realtime get component adds SolrDocuments to the response without running them though the transformer -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
