Streaming expression with JDBC source returns no data for long running queries.

[Rishabh Patel <ri...@gmail.com>]

Hello,

I have created a Solr collection with 4 shards and 4 replicas. Now in the
UI, I am trying to fetch data from Hive JDBC source using streaming
expressions. The query executes successfully if I limit it to ~100000 rows.
With more rows, after about 10 seconds, the waiting spinner is gone and no
results are returned. There are no errors in the Solr logs or in the Hive
logs.

Here is the sample query

jdbc(
          connection="jdbc:hive2://node1.com:10000/default",
          sql="select * from default.temp limit 1000000",
          sort="id asc",
          driver="org.apache.hive.jdbc.HiveDriver")

Hive has executed the query successfully but the data is not displayed by
Solr. The same happens when the query is executed via curl. Is this
behaviour expected?

-- 
Regards,
*Rishabh Patel*

Re: Streaming expression with JDBC source returns no data for long running queries.

[Joel Bernstein <jo...@gmail.com>]

The JdbcStream is pretty much just a wrapper for the JDBC driver. I don't
believe the size of the result set would have much effect on the JdbcStream.

Joel Bernstein
http://joelsolr.blogspot.com/

On Wed, Apr 5, 2017 at 6:35 PM, Rishabh Patel <
rishabh.mahendra.patel@gmail.com> wrote:

> Hello,
>
> I have created a Solr collection with 4 shards and 4 replicas. Now in the
> UI, I am trying to fetch data from Hive JDBC source using streaming
> expressions. The query executes successfully if I limit it to ~100000 rows.
> With more rows, after about 10 seconds, the waiting spinner is gone and no
> results are returned. There are no errors in the Solr logs or in the Hive
> logs.
>
> Here is the sample query
>
> jdbc(
>           connection="jdbc:hive2://node1.com:10000/default",
>           sql="select * from default.temp limit 1000000",
>           sort="id asc",
>           driver="org.apache.hive.jdbc.HiveDriver")
>
> Hive has executed the query successfully but the data is not displayed by
> Solr. The same happens when the query is executed via curl. Is this
> behaviour expected?
>
> --
> Regards,
> *Rishabh Patel*
>