[
https://issues.apache.org/jira/browse/SOLR-8507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101933#comment-15101933
]
Kevin Risden edited comment on SOLR-8507 at 1/15/16 3:48 PM:
-------------------------------------------------------------
I'm running into an issue when writing tests for the versions. The logic
currently relies on querying /admin/info/system and pulling out the
solr-spec-version. This doesn't seem to be populated during the tests if I
query the test cluster. I found the following from SystemInfoHandler and
p.getSpecificationVersion() is null during the tests. When I query that same
url on a running Solr server from a trunk build it works just fine.
{code}
private static SimpleOrderedMap<Object> getLuceneInfo() {
SimpleOrderedMap<Object> info = new SimpleOrderedMap<>();
Package p = SolrCore.class.getPackage();
info.add( "solr-spec-version", p.getSpecificationVersion() );
info.add( "solr-impl-version", p.getImplementationVersion() );
p = LucenePackage.class.getPackage();
info.add( "lucene-spec-version", p.getSpecificationVersion() );
info.add( "lucene-impl-version", p.getImplementationVersion() );
return info;
}
{code}
I compared the solrconfig-sql.xml to the one that is the default shipped with
Solr. So two questions:
1) is the version not being populated since its not a full build?
2) if #1 is true, what is a better way to query the Solr Cluster versions?
was (Author: risdenk):
I'm running into an issue when writing tests for the versions. The logic
currently relies on querying /admin/info/system and pulling out the
solr-spec-version. This doesn't seem to be populated during the tests if I
query the test cluster. I found the following from SystemInfoHandler and
p.getSpecificationVersion() is null during the tests. When I query that same
url on a trunk build it works just fine.
{code}
private static SimpleOrderedMap<Object> getLuceneInfo() {
SimpleOrderedMap<Object> info = new SimpleOrderedMap<>();
Package p = SolrCore.class.getPackage();
info.add( "solr-spec-version", p.getSpecificationVersion() );
info.add( "solr-impl-version", p.getImplementationVersion() );
p = LucenePackage.class.getPackage();
info.add( "lucene-spec-version", p.getSpecificationVersion() );
info.add( "lucene-impl-version", p.getImplementationVersion() );
return info;
}
{code}
I compared the solrconfig-sql.xml to the one that is the default shipped with
Solr. So two questions:
1) is the version not being populated since its not a full build?
2) if #1 is true, what is a better way to query the Solr Cluster versions?
> Add information about database product name, product version, driver name,
> and driver version.
> ----------------------------------------------------------------------------------------------
>
> Key: SOLR-8507
> URL: https://issues.apache.org/jira/browse/SOLR-8507
> Project: Solr
> Issue Type: Sub-task
> Components: SolrJ
> Affects Versions: Trunk
> Reporter: Kevin Risden
> Attachments: SOLR-8507.patch
>
>
> DBVisualizer asks for information about database product name, product
> version, driver name, and driver version. These should be implemented in
> DatabaseMetaDataImpl.
> 2016-01-07 13:30:10.814 FINE 83 [pool-3-thread-10 - E.ￄﾁ] RootConnection:
> DatabaseMetaDataImpl.getDatabaseProductName()
> 2016-01-07 13:30:10.814 FINE 83 [pool-3-thread-10 - E.ￄﾁ] RootConnection:
> DatabaseMetaDataImpl.getDatabaseProductVersion()
> 2016-01-07 13:30:10.814 FINE 83 [pool-3-thread-10 - E.ￄﾁ] RootConnection:
> DatabaseMetaDataImpl.getDriverName()
> 2016-01-07 13:30:10.814 FINE 83 [pool-3-thread-10 - E.ￄﾁ] RootConnection:
> DatabaseMetaDataImpl.getDriverVersion()
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
