[jira] [Commented] (SOLR-11229) Add a configuration upgrade tool for Solr
[ https://issues.apache.org/jira/browse/SOLR-11229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16456107#comment-16456107 ] Uwe Schindler commented on SOLR-11229: -- The XSL specialist talks here: Yes, stuff like converting a schema XML document or a solrconfig.xml is the typical use case of XSL. XSL can be configured with parameters. So, yes use XSL for all stuff involving XML-based config files. Code written in Java is unreadable. P.S.: XSL is touring-complete (hahaha) > Add a configuration upgrade tool for Solr > - > > Key: SOLR-11229 > URL: https://issues.apache.org/jira/browse/SOLR-11229 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 6.6 >Reporter: Hrishikesh Gadre >Priority: Major > > Despite widespread enterprise adoption, Solr lacks automated upgrade tooling. > It has long been a challenge for users to understand the implications of a > Solr upgrade. Users must manually review the Solr release notes to identify > configuration changes either to fix backwards incompatibilities or to utilize > latest features in the new version. Additionally, users must identify a way > to migrate existing index data to the new version (either via an index > upgrade or re-indexing the raw data). > Solr config upgrade tool aims to simplify the upgrade process by providing > upgrade instructions tailored to your configuration. These instructions can > help you to answer following questions > - Does my Solr configuration have any backwards incompatible sections? If yes > which ones? > - For each of the incompatibility - what do I need to do to fix this > incompatibility? Where can I get more information about why this > incompatibility was introduced (e.g. references to Lucene/Solr jiras)? > - Are there any changes in Lucene/Solr which would require me to do a full > reindexing OR can I get away with an index upgrade? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11229) Add a configuration upgrade tool for Solr
[
https://issues.apache.org/jira/browse/SOLR-11229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16456091#comment-16456091
]
Jan Høydahl commented on SOLR-11229:
{quote}Eventually we would like to incorporate this tool as part of the SOLR
distribution if there is enough interest from the community.
{quote}
I saw your talk in Las Vegas and think that this effort is of benefit for many.
More important than where the tool lives is that it gets exposed through
RefGuide and maintained for each version. Are you also making tooling in
Cloudera to upgrade from Trie to Point fields etc or do you use a reindex from
source strategy (guessing the latter)?
> Add a configuration upgrade tool for Solr
> -
>
> Key: SOLR-11229
> URL: https://issues.apache.org/jira/browse/SOLR-11229
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
>Affects Versions: 6.6
>Reporter: Hrishikesh Gadre
>Priority: Major
>
> Despite widespread enterprise adoption, Solr lacks automated upgrade tooling.
> It has long been a challenge for users to understand the implications of a
> Solr upgrade. Users must manually review the Solr release notes to identify
> configuration changes either to fix backwards incompatibilities or to utilize
> latest features in the new version. Additionally, users must identify a way
> to migrate existing index data to the new version (either via an index
> upgrade or re-indexing the raw data).
> Solr config upgrade tool aims to simplify the upgrade process by providing
> upgrade instructions tailored to your configuration. These instructions can
> help you to answer following questions
> - Does my Solr configuration have any backwards incompatible sections? If yes
> which ones?
> - For each of the incompatibility - what do I need to do to fix this
> incompatibility? Where can I get more information about why this
> incompatibility was introduced (e.g. references to Lucene/Solr jiras)?
> - Are there any changes in Lucene/Solr which would require me to do a full
> reindexing OR can I get away with an index upgrade?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11229) Add a configuration upgrade tool for Solr
[ https://issues.apache.org/jira/browse/SOLR-11229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16455565#comment-16455565 ] Mark Miller commented on SOLR-11229: bq. I'm curious about the choice of XSLT here. I have never been a fan of XSLT, but in this case it actually ends up being pretty nice for this use case. That is a first for me. Referencing existing rules to add new ones makes it fairly easy even for someone that is doing their best to never understand more than 5% of XSLT. > Add a configuration upgrade tool for Solr > - > > Key: SOLR-11229 > URL: https://issues.apache.org/jira/browse/SOLR-11229 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 6.6 >Reporter: Hrishikesh Gadre >Priority: Major > > Despite widespread enterprise adoption, Solr lacks automated upgrade tooling. > It has long been a challenge for users to understand the implications of a > Solr upgrade. Users must manually review the Solr release notes to identify > configuration changes either to fix backwards incompatibilities or to utilize > latest features in the new version. Additionally, users must identify a way > to migrate existing index data to the new version (either via an index > upgrade or re-indexing the raw data). > Solr config upgrade tool aims to simplify the upgrade process by providing > upgrade instructions tailored to your configuration. These instructions can > help you to answer following questions > - Does my Solr configuration have any backwards incompatible sections? If yes > which ones? > - For each of the incompatibility - what do I need to do to fix this > incompatibility? Where can I get more information about why this > incompatibility was introduced (e.g. references to Lucene/Solr jiras)? > - Are there any changes in Lucene/Solr which would require me to do a full > reindexing OR can I get away with an index upgrade? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11229) Add a configuration upgrade tool for Solr
[ https://issues.apache.org/jira/browse/SOLR-11229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16455561#comment-16455561 ] Hrishikesh Gadre commented on SOLR-11229: - [~janhoy] Yes, although the new development for this tool is happening in the internal cloudera repo. It includes the upgrade rules for Solr 6 -> 7 upgrade as well. I will sync the public github repository ASAP. Eventually we would like to incorporate this tool as part of the SOLR distribution if there is enough interest from the community. > Add a configuration upgrade tool for Solr > - > > Key: SOLR-11229 > URL: https://issues.apache.org/jira/browse/SOLR-11229 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 6.6 >Reporter: Hrishikesh Gadre >Priority: Major > > Despite widespread enterprise adoption, Solr lacks automated upgrade tooling. > It has long been a challenge for users to understand the implications of a > Solr upgrade. Users must manually review the Solr release notes to identify > configuration changes either to fix backwards incompatibilities or to utilize > latest features in the new version. Additionally, users must identify a way > to migrate existing index data to the new version (either via an index > upgrade or re-indexing the raw data). > Solr config upgrade tool aims to simplify the upgrade process by providing > upgrade instructions tailored to your configuration. These instructions can > help you to answer following questions > - Does my Solr configuration have any backwards incompatible sections? If yes > which ones? > - For each of the incompatibility - what do I need to do to fix this > incompatibility? Where can I get more information about why this > incompatibility was introduced (e.g. references to Lucene/Solr jiras)? > - Are there any changes in Lucene/Solr which would require me to do a full > reindexing OR can I get away with an index upgrade? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11229) Add a configuration upgrade tool for Solr
[ https://issues.apache.org/jira/browse/SOLR-11229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16455457#comment-16455457 ] Jan Høydahl commented on SOLR-11229: Is this tool useful as is? > Add a configuration upgrade tool for Solr > - > > Key: SOLR-11229 > URL: https://issues.apache.org/jira/browse/SOLR-11229 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 6.6 >Reporter: Hrishikesh Gadre >Priority: Major > > Despite widespread enterprise adoption, Solr lacks automated upgrade tooling. > It has long been a challenge for users to understand the implications of a > Solr upgrade. Users must manually review the Solr release notes to identify > configuration changes either to fix backwards incompatibilities or to utilize > latest features in the new version. Additionally, users must identify a way > to migrate existing index data to the new version (either via an index > upgrade or re-indexing the raw data). > Solr config upgrade tool aims to simplify the upgrade process by providing > upgrade instructions tailored to your configuration. These instructions can > help you to answer following questions > - Does my Solr configuration have any backwards incompatible sections? If yes > which ones? > - For each of the incompatibility - what do I need to do to fix this > incompatibility? Where can I get more information about why this > incompatibility was introduced (e.g. references to Lucene/Solr jiras)? > - Are there any changes in Lucene/Solr which would require me to do a full > reindexing OR can I get away with an index upgrade? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11229) Add a configuration upgrade tool for Solr
[ https://issues.apache.org/jira/browse/SOLR-11229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16133497#comment-16133497 ] Hrishikesh Gadre commented on SOLR-11229: - [~gerlowskija] Thanks for your feedback. bq. I noticed that the TODO list in the README.md doesn't mention anything about Windows support. Is a Windows version of this script in the scope of this JIRA? Or is the idea that it'd be added as a part of a separate JIRA later on? Sure - we can add windows support as part of this jira itself. I didn't think about Windows support earlier. bq. I notice that ConfigUpgradeTool mimics but doesnt technically implement the Solr Tool interface. Is the idea that as this makes its way into Solr, it would actually implement that interface? Or is it coincidence that those classes look similar. This is not a suggestion or a critique; just trying to understand the code a little better. Sure I think it would be a good idea to use Solr Tool interface for this tool as well. bq. I'm curious about the choice of XSLT here. One of the important requirement is the ability to accept a Solr configuration file (e.g. solrconfig.xml) of version X and emit a identical configuration compatible with version Y (e.g. rewriting some of the configuration sections). As per my understanding XSLT is designed for such use-cases (while XPath is more useful towards querying the XML document). Obviously we can cobble together some java/bash code along with XPath to make it work. But I felt using a single technology to handle both querying and transformation would simplify the tool as well as implementation of upgrade rules. Note - I personally found XSLT to be adequate to implement all the upgrade rules from Solr 4 -> Solr 6. It took me about an 1 1/2 to read the Upgrade section in the release notes and implement the upgrade rules for one release (e.g. from Solr 4 -> Solr 5). And now we have some reference available, new rules can easily be added by referring to these definitions. > Add a configuration upgrade tool for Solr > - > > Key: SOLR-11229 > URL: https://issues.apache.org/jira/browse/SOLR-11229 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 6.6 >Reporter: Hrishikesh Gadre > > Despite widespread enterprise adoption, Solr lacks automated upgrade tooling. > It has long been a challenge for users to understand the implications of a > Solr upgrade. Users must manually review the Solr release notes to identify > configuration changes either to fix backwards incompatibilities or to utilize > latest features in the new version. Additionally, users must identify a way > to migrate existing index data to the new version (either via an index > upgrade or re-indexing the raw data). > Solr config upgrade tool aims to simplify the upgrade process by providing > upgrade instructions tailored to your configuration. These instructions can > help you to answer following questions > - Does my Solr configuration have any backwards incompatible sections? If yes > which ones? > - For each of the incompatibility - what do I need to do to fix this > incompatibility? Where can I get more information about why this > incompatibility was introduced (e.g. references to Lucene/Solr jiras)? > - Are there any changes in Lucene/Solr which would require me to do a full > reindexing OR can I get away with an index upgrade? -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11229) Add a configuration upgrade tool for Solr
[ https://issues.apache.org/jira/browse/SOLR-11229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124693#comment-16124693 ] Jason Gerlowski commented on SOLR-11229: Hey [~hgadre], took a quick look at the tool you mentioned above. Had a few questions/suggestions: - I noticed that the TODO list in the README.md doesn't mention anything about Windows support. Is a Windows version of this script in the scope of this JIRA? Or is the idea that it'd be added as a part of a separate JIRA later on? - I'm curious about the choice of XSLT here. XSLT isn't rocket science, but it does have its traps, and it's another thing maintainers (and users) will have to dig into. At a quick glance, much of the XSLT logic could also be done with xpath (in bash, or invoked from Java-land)...though it's totally possible I missed something. Did you consider the maintenance tradeoff between XSLT and Java? Or the test-ability tradeoff? Or is there maybe a reason I'm missing that makes XSLT required? - I notice that [ConfigUpgradeTool|https://github.com/hgadre/solr-upgrade-tool/blob/master/src/main/java/org/apache/solr/config/upgrade/ConfigUpgradeTool.java] mimics but doesnt technically implement the Solr [Tool|https://github.com/apache/lucene-solr/blob/93ed4770ac82eb732c7409f82d02009e0fabe390/solr/core/src/java/org/apache/solr/util/SolrCLI.java#L139] interface. Is the idea that as this makes its way into Solr, it would actually implement that interface? Or is it coincidence that those classes look similar. This is not a suggestion or a critique; just trying to understand the code a little better. > Add a configuration upgrade tool for Solr > - > > Key: SOLR-11229 > URL: https://issues.apache.org/jira/browse/SOLR-11229 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 6.6 >Reporter: Hrishikesh Gadre > > Despite widespread enterprise adoption, Solr lacks automated upgrade tooling. > It has long been a challenge for users to understand the implications of a > Solr upgrade. Users must manually review the Solr release notes to identify > configuration changes either to fix backwards incompatibilities or to utilize > latest features in the new version. Additionally, users must identify a way > to migrate existing index data to the new version (either via an index > upgrade or re-indexing the raw data). > Solr config upgrade tool aims to simplify the upgrade process by providing > upgrade instructions tailored to your configuration. These instructions can > help you to answer following questions > - Does my Solr configuration have any backwards incompatible sections? If yes > which ones? > - For each of the incompatibility - what do I need to do to fix this > incompatibility? Where can I get more information about why this > incompatibility was introduced (e.g. references to Lucene/Solr jiras)? > - Are there any changes in Lucene/Solr which would require me to do a full > reindexing OR can I get away with an index upgrade? -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11229) Add a configuration upgrade tool for Solr
[ https://issues.apache.org/jira/browse/SOLR-11229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123975#comment-16123975 ] Hrishikesh Gadre commented on SOLR-11229: - The initial prototype of this tool is available @ https://github.com/hgadre/solr-upgrade-tool > Add a configuration upgrade tool for Solr > - > > Key: SOLR-11229 > URL: https://issues.apache.org/jira/browse/SOLR-11229 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 6.6 >Reporter: Hrishikesh Gadre > > Despite widespread enterprise adoption, Solr lacks automated upgrade tooling. > It has long been a challenge for users to understand the implications of a > Solr upgrade. Users must manually review the Solr release notes to identify > configuration changes either to fix backwards incompatibilities or to utilize > latest features in the new version. Additionally, users must identify a way > to migrate existing index data to the new version (either via an index > upgrade or re-indexing the raw data). > Solr config upgrade tool aims to simplify the upgrade process by providing > upgrade instructions tailored to your configuration. These instructions can > help you to answer following questions > - Does my Solr configuration have any backwards incompatible sections? If yes > which ones? > - For each of the incompatibility - what do I need to do to fix this > incompatibility? Where can I get more information about why this > incompatibility was introduced (e.g. references to Lucene/Solr jiras)? > - Are there any changes in Lucene/Solr which would require me to do a full > reindexing OR can I get away with an index upgrade? -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
