Also since the same query is working from curl, it's a pretty strong indication that the error is occurring on the client. The logs show that the includeMetadata parameter is being sent properly. This is done automatically by the JDBC driver. So the /sql handler should be sending the metadata Tuple. The error you are seeing will occur if the metadata Tuple is not present or if the first Tuple is null. My guess is the first Tuple is null do to a ClassNotFoundException which is getting swallowed up during the parse.
Joel Bernstein http://joelsolr.blogspot.com/ On Thu, May 5, 2016 at 8:37 AM, Joel Bernstein <[email protected]> wrote: > In looking at the logs things look good on the server side. The sql query > is sent to the /sql handler. It's translated to a solr query and sent to > the select handler. Results are returned and no errors. > > So, I'm going to venture a guess that problem is on the client side. I'm > wondering if you're tripping a ClassNotFoundException once the parsing of > the json result comes back. I've seen instances where > ClassNotFoundExceptions get swallowed. > > Can you post your classpath? > > > > Joel Bernstein > http://joelsolr.blogspot.com/ > > On Thu, May 5, 2016 at 4:57 AM, deniz <[email protected]> wrote: > >> Also found >> >> // JDBC requires metadata like field names from the SQLHandler. Force >> this property to be true. >> props.setProperty("includeMetadata", "true"); >> >> >> in org.apache.solr.client.solrj.io.sql.DriverImpl >> >> are there any other ways to get response on solrj without metaData to >> avoid >> the error? >> >> >> >> ----- >> Zeki ama calismiyor... Calissa yapar... >> -- >> View this message in context: >> http://lucene.472066.n3.nabble.com/Solr-6-Solrj-RuntimeException-First-tuple-is-not-a-metadata-tuple-tp4274451p4274739.html >> Sent from the Solr - User mailing list archive at Nabble.com. >> > >
