lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-1621) Allow current single core deployments to be specified by solr.xml
Date Tue, 08 Dec 2009 19:53:18 GMT

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

Hoss Man commented on SOLR-1621:
--------------------------------

The nice thing about the *idea* of ALIAS is that you can have cores with very explicit names
(ie: catalog_v1, catalog_v2, etc...) and then you can have aliases like "LIVE" and "EXPERIMENTAL"
that you can move around as needed.  Similar things can be accomplished with the SWAP command,
but it's more limiting.

That said: the last time i tired using ALIAS it was such a confusing pain in the ass because
of the way the original name was still tracked separately from the list of aliases, even if
that name had been taken over by another core) i couldn't bring myself to use it -- using
SWAP and keeping track of the logical names externally was less confusing.

If we can make ALIAS work well, it will kick ass -- but we can always yank it for now if it's
in our way, and add it back again later if someone comes up with a good way to do it.  (it
was probably a mistake to try and treat names an aliases as equals in the first place ...
looking up a core by a "string" is probably the only use cases where they should be treated
equally, all of the other CoreAdmin commands should really differentiate.)

> Allow current single core deployments to be specified by solr.xml
> -----------------------------------------------------------------
>
>                 Key: SOLR-1621
>                 URL: https://issues.apache.org/jira/browse/SOLR-1621
>             Project: Solr
>          Issue Type: New Feature
>    Affects Versions: 1.5
>            Reporter: Noble Paul
>             Fix For: 1.5
>
>         Attachments: SOLR-1621.patch, SOLR-1621.patch, SOLR-1621.patch, SOLR-1621.patch,
SOLR-1621.patch, SOLR-1621.patch
>
>
> supporting two different modes of deployments is turning out to be hard. This leads to
duplication of code. Moreover there is a lot of confusion on where do we put common configuration.
See the mail thread http://markmail.org/message/3m3rqvp2ckausjnf

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


Mime
View raw message