Re: JNDI in db-data-config.xml websphere
Have to use exact JNDI name in db-data-config.xml, as unmanaged threads in Websphere do not have access to java:comp/env namespace. Resource name can not be mapped to websphere jdbc datasource name via reference definition in web.xml. Now using jndiName=jdbc/testdb instead of jndiName=java:comp/env/jdbc/testdb and also defining websphere JDBC datasource as jdbc/testdb -- View this message in context: http://lucene.472066.n3.nabble.com/JNDI-in-db-data-config-xml-websphere-tp3884787p3896869.html Sent from the Solr - User mailing list archive at Nabble.com.
JNDI in db-data-config.xml websphere
I am trying to use jndiName attribute in db-data-config.xml. This works great in tomcat. However having issues in websphere. Following exception is thrown Make sure that a J2EE application does not execute JNDI operations on java: names within static code blocks or in threads created by that J2EE application. Such code does not necessarily run on the thread of a server application request and therefore is not supported by JNDI operations on java: names. [Root exception is javax.naming.NameNotFoundException: Name comp/env/jdbc not found in context java:. It seems like websphere has issues accessing jndi resource from Static code. Has anyone experienced this ? Thanks Regards -- View this message in context: http://lucene.472066.n3.nabble.com/JNDI-in-db-data-config-xml-websphere-tp3884787p3884787.html Sent from the Solr - User mailing list archive at Nabble.com.
Document with longer field names and many fields
We are planning to import data from various tables of ERP DB into a single Solr/Lucene index. Since these tables have overlapping columns we are planing to name the corresponding document field as table_name_column_name. I have following questions on this. 1) Does having long field name (table_name_column_name) affect performance ? 2) We will end up with close to 200 fields per document in schema definition. At time of document storage only 20 field per will be indexed and stored for each stored document. Is there a limitation here, are we creating performance bottleneck by designing schema this way ? Thanks Vijay -- View this message in context: http://lucene.472066.n3.nabble.com/Document-with-longer-field-names-and-many-fields-tp3703077p3703077.html Sent from the Solr - User mailing list archive at Nabble.com.
Solrj 3.3.0 Method SolrQuery.setSortField not working
When setting SolrQuery.setSortField(field1, ORDER.asc) on SolrQuery is not adding sort parameter to Solr query. Has anyone faced this issue ? -- View this message in context: http://lucene.472066.n3.nabble.com/Solrj-3-3-0-Method-SolrQuery-setSortField-not-working-tp3481239p3481239.html Sent from the Solr - User mailing list archive at Nabble.com.
DataImportHandler frequency
I working with a transactional system with RDBMS. We have approximately 200 db transaction per minute at peak usage. I am planning to use Solr for indexing various part of data. I wanted to keep Solr indexes as up to date as possible, so the the search result returned to user are as fresh and actionable as possible. Wanted to check if there is a guidance on frequency for running delta-import. I was thinking of running it every 1 minute. It is better to post document as part of online transaction or better to run data import every minute ? -- View this message in context: http://lucene.472066.n3.nabble.com/DataImportHandler-frequency-tp3382712p3382712.html Sent from the Solr - User mailing list archive at Nabble.com.
