[jira] Created: (SOLR-975) admin-extra.html not currectly display when using multicore configuration

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (SOLR-975) admin-extra.html not currectly display when using multicore configuration

ASF GitHub Bot (Jira)
admin-extra.html not currectly display when using multicore configuration
-------------------------------------------------------------------------

                 Key: SOLR-975
                 URL: https://issues.apache.org/jira/browse/SOLR-975
             Project: Solr
          Issue Type: Bug
          Components: web gui
    Affects Versions: 1.4
         Environment: Jetty openjdk 1.6.0 1.0.b12 (EPEL package for EL5)
            Reporter: Edward Rudd


I'm having "cross-talk" issues with using the Solr nightlies (and probably w/ 1.3.0 release but have not tested as I needed newer features of the DataImportHandler in the nightlies)

Basic scenario for this bug is as follows

I have two cores configured and BOTH have a customized "admin-extra.html", however going to the admin pages uses the SAME admin-extra.html for all cores.   the one used is whichever core is browsed first..    This looks like a caching bug where the cache is not taking into account the Core.

Basically my admin-extra.html has a link to the data importer script and a link to reload the core (which has to have the core name explicitly in the per-core admin-extra.html).

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (SOLR-975) admin-extra.html not currectly display when using multicore configuration

ASF GitHub Bot (Jira)

    [ https://issues.apache.org/jira/browse/SOLR-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859553#action_12859553 ]

Hoss Man commented on SOLR-975:
-------------------------------

support for admin-extras.html has always been a hack ... the implementation only ever worked for single core setups because it depended on functionality that took advantage of the singleton.

a fix should be possible, but it might make more sense to just scrap the idea of a magicly named HTML snippet file that is included verbatim (in the middle of an open table tag no less) and come up with a more intuitive and robust way to let people configure what should appear on the admin screen

> admin-extra.html not currectly display when using multicore configuration
> -------------------------------------------------------------------------
>
>                 Key: SOLR-975
>                 URL: https://issues.apache.org/jira/browse/SOLR-975
>             Project: Solr
>          Issue Type: Bug
>          Components: web gui
>    Affects Versions: 1.4
>         Environment: Jetty openjdk 1.6.0 1.0.b12 (EPEL package for EL5)
>            Reporter: Edward Rudd
>
> I'm having "cross-talk" issues with using the Solr nightlies (and probably w/ 1.3.0 release but have not tested as I needed newer features of the DataImportHandler in the nightlies)
> Basic scenario for this bug is as follows
> I have two cores configured and BOTH have a customized "admin-extra.html", however going to the admin pages uses the SAME admin-extra.html for all cores.   the one used is whichever core is browsed first..    This looks like a caching bug where the cache is not taking into account the Core.
> Basically my admin-extra.html has a link to the data importer script and a link to reload the core (which has to have the core name explicitly in the per-core admin-extra.html).

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (SOLR-975) admin-extra.html not currectly display when using multicore configuration

ASF GitHub Bot (Jira)
In reply to this post by ASF GitHub Bot (Jira)

    [ https://issues.apache.org/jira/browse/SOLR-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859584#action_12859584 ]

Edward Rudd commented on SOLR-975:
----------------------------------

I agree that a real more robust system should be built..  Abusing the tables with badly formatted HTML to do what is currently being done is HORRID.

Any suggestions on a "cleaner" way of doing this? and which source files do I need to tear apart? (I'll work on a patch)

> admin-extra.html not currectly display when using multicore configuration
> -------------------------------------------------------------------------
>
>                 Key: SOLR-975
>                 URL: https://issues.apache.org/jira/browse/SOLR-975
>             Project: Solr
>          Issue Type: Bug
>          Components: web gui
>    Affects Versions: 1.4
>         Environment: Jetty openjdk 1.6.0 1.0.b12 (EPEL package for EL5)
>            Reporter: Edward Rudd
>
> I'm having "cross-talk" issues with using the Solr nightlies (and probably w/ 1.3.0 release but have not tested as I needed newer features of the DataImportHandler in the nightlies)
> Basic scenario for this bug is as follows
> I have two cores configured and BOTH have a customized "admin-extra.html", however going to the admin pages uses the SAME admin-extra.html for all cores.   the one used is whichever core is browsed first..    This looks like a caching bug where the cache is not taking into account the Core.
> Basically my admin-extra.html has a link to the data importer script and a link to reload the core (which has to have the core name explicitly in the per-core admin-extra.html).

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]