[jira] [Commented] (SOLR-4983) Problematic core naming by collection create API
[ https://issues.apache.org/jira/browse/SOLR-4983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840003#comment-13840003 ] Artem Karpenko commented on SOLR-4983: -- While this is not resolved - could anyone suggest if by creating cores separately (with the same collection name) we would achieve the same effect as creating collection via Collections API? Trying to do so seems to produce desired result, but maybe there are some hidden (and important) difference? > Problematic core naming by collection create API > - > > Key: SOLR-4983 > URL: https://issues.apache.org/jira/browse/SOLR-4983 > Project: Solr > Issue Type: Bug > Components: SolrCloud >Reporter: Chris Toomey > > The SolrCloud collection create API creates cores named > "foo_shard_replica" when asked to create collection "foo". > This is problematic for at least 2 reasons: > 1) these ugly core names show up in the core admin UI, and will vary > depending on which node is being used, > 2) it prevents collections from being used in SolrCloud joins, since join > takes a core name as the fromIndex parameter and there's no single core name > for the collection. As I've documented in > https://issues.apache.org/jira/browse/SOLR-4905 and > http://lucene.472066.n3.nabble.com/Joins-with-SolrCloud-tp4073199p4074038.html, > SolrCloud join does work when the inner collection (fromIndex) is not > sharded, assuming that collection is available and initialized at SolrCloud > bootstrap time. > Could this be changed to instead use the collection name for the core name? > Or at least add a core-name option to the API? -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-5159) Manifest includes non-parsed maven variables
[
https://issues.apache.org/jira/browse/SOLR-5159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742480#comment-13742480
]
Artem Karpenko commented on SOLR-5159:
--
Great, thank you Steve, I was glad to help.
> Manifest includes non-parsed maven variables
>
>
> Key: SOLR-5159
> URL: https://issues.apache.org/jira/browse/SOLR-5159
> Project: Solr
> Issue Type: Bug
> Components: Build
>Affects Versions: 4.4, 4.5, 5.0
> Environment: Apache Maven 3.0.5
>Reporter: Artem Karpenko
>Assignee: Steve Rowe
>Priority: Minor
> Labels: maven-bundle-plugin, maven3,
> Fix For: 4.5, 5.0
>
> Attachments: SOLR-5159.patch
>
>
> When building Lucene/Solr with Apache Maven 3, all MANIFEST.MF files included
> into JAR artifacts contain non-parsed POM variables: namely, there are
> entries like
> Specification-Version: 5.0.0.$\{now.version}
> In the end, Solr displays these values on admin page in "Versions" section.
> This is caused by unresolved bug in maven-bundle-plugin (FELIX-3392).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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] [Commented] (SOLR-5159) Manifest includes non-parsed maven variables
[
https://issues.apache.org/jira/browse/SOLR-5159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741061#comment-13741061
]
Artem Karpenko commented on SOLR-5159:
--
I've checked maven 2 builds as well - after applying changes manifest files
stay the same (correct).
> Manifest includes non-parsed maven variables
>
>
> Key: SOLR-5159
> URL: https://issues.apache.org/jira/browse/SOLR-5159
> Project: Solr
> Issue Type: Bug
> Components: Build
>Affects Versions: 4.4, 4.5, 5.0
> Environment: Apache Maven 3.0.5
>Reporter: Artem Karpenko
>Priority: Minor
> Labels: maven-bundle-plugin, maven3,
> Attachments: SOLR-5159.patch
>
>
> When building Lucene/Solr with Apache Maven 3, all MANIFEST.MF files included
> into JAR artifacts contain non-parsed POM variables: namely, there are
> entries like
> Specification-Version: 5.0.0.$\{now.version}
> In the end, Solr displays these values on admin page in "Versions" section.
> This is caused by unresolved bug in maven-bundle-plugin (FELIX-3392).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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] [Updated] (SOLR-5159) Manifest includes non-parsed maven variables
[
https://issues.apache.org/jira/browse/SOLR-5159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Karpenko updated SOLR-5159:
-
Description:
When building Lucene/Solr with Apache Maven 3, all MANIFEST.MF files included
into JAR artifacts contain non-parsed POM variables: namely, there are entries
like
Specification-Version: 5.0.0.$\{now.version}
In the end, Solr displays these values on admin page in "Versions" section.
This is caused by unresolved bug in maven-bundle-plugin (FELIX-3392).
was:
When building Lucene/Solr with Apache Maven 3, all MANIFEST.MF files included
into JAR artifacts contain non-parsed POM variables: namely, there are entries
like
Specification-Version: 5.0.0.${now.version}
In the end, Solr displays these values on admin page in "Versions" section.
This is caused by unresolved bug in maven-bundle-plugin (FELIX-3392).
> Manifest includes non-parsed maven variables
>
>
> Key: SOLR-5159
> URL: https://issues.apache.org/jira/browse/SOLR-5159
> Project: Solr
> Issue Type: Bug
> Components: Build
>Affects Versions: 4.4, 4.5, 5.0
> Environment: Apache Maven 3.0.5
>Reporter: Artem Karpenko
>Priority: Minor
> Labels: maven-bundle-plugin, maven3,
> Attachments: SOLR-5159.patch
>
>
> When building Lucene/Solr with Apache Maven 3, all MANIFEST.MF files included
> into JAR artifacts contain non-parsed POM variables: namely, there are
> entries like
> Specification-Version: 5.0.0.$\{now.version}
> In the end, Solr displays these values on admin page in "Versions" section.
> This is caused by unresolved bug in maven-bundle-plugin (FELIX-3392).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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] [Updated] (SOLR-5159) Manifest includes non-parsed maven variables
[
https://issues.apache.org/jira/browse/SOLR-5159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Karpenko updated SOLR-5159:
-
Attachment: SOLR-5159.patch
Patch moves declaration of Manifest headers from archive configuration of
maven-jar-plugin into "instructions" section of maven-bundle-plugin, which
latter plugin does parse for variables correctly.
> Manifest includes non-parsed maven variables
>
>
> Key: SOLR-5159
> URL: https://issues.apache.org/jira/browse/SOLR-5159
> Project: Solr
> Issue Type: Bug
> Components: Build
>Affects Versions: 4.4, 4.5, 5.0
> Environment: Apache Maven 3.0.5
>Reporter: Artem Karpenko
>Priority: Minor
> Labels: maven-bundle-plugin, maven3,
> Attachments: SOLR-5159.patch
>
>
> When building Lucene/Solr with Apache Maven 3, all MANIFEST.MF files included
> into JAR artifacts contain non-parsed POM variables: namely, there are
> entries like
> Specification-Version: 5.0.0.${now.version}
> In the end, Solr displays these values on admin page in "Versions" section.
> This is caused by unresolved bug in maven-bundle-plugin (FELIX-3392).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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-5159) Manifest includes non-parsed maven variables
Artem Karpenko created SOLR-5159:
Summary: Manifest includes non-parsed maven variables
Key: SOLR-5159
URL: https://issues.apache.org/jira/browse/SOLR-5159
Project: Solr
Issue Type: Bug
Components: Build
Affects Versions: 4.4, 4.5, 5.0
Environment: Apache Maven 3.0.5
Reporter: Artem Karpenko
Priority: Minor
When building Lucene/Solr with Apache Maven 3, all MANIFEST.MF files included
into JAR artifacts contain non-parsed POM variables: namely, there are entries
like
Specification-Version: 5.0.0.${now.version}
In the end, Solr displays these values on admin page in "Versions" section.
This is caused by unresolved bug in maven-bundle-plugin (FELIX-3392).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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
