Hi guys!
I agree with Boris that this feature (ability to issue multiple Hive
queries simultaneously) is extremely important as people use Hive
interpereter not only against Hive but against other systems, too.
Predominantly RDBMS.
Making changes in source code by ourselves (not to mention without tests)
leads to incomatibility with future releases and doesnt' solve problem.
On Fri, Jun 10, 2016 at 10:22 PM, Prasad Wagle <prasadwa...@gmail.com>
wrote:
> Hi Boris,
>
> You can run concurrent queries by overriding the getScheduler function in
> JDBCInterpreter to return ParallelScheduler like HiveInterpreter.
>
> @jongyoul - should we change JDBCInterpreter. getScheduler to return
> ParallelScheduler? It would also be nice to make maxConcurrency
> configurable.
>
> JDBCInterpreter:
> @Override
> public Scheduler getScheduler() {
> return SchedulerFactory.singleton().createOrGetFIFOScheduler(
> JDBCInterpreter.class.getName() + this.hashCode());
> }
>
> HiveInterpreter:
> @Override
> public Scheduler getScheduler() {
> return SchedulerFactory.singleton().createOrGetParallelScheduler(
> HiveInterpreter.class.getName() + this.hashCode(), 10);
> }
>
> Thanks,
> Prasad
>
> On Fri, Jun 10, 2016 at 5:52 AM, Boris Schminke <schmink...@gmail.com>
> wrote:
>
>> Hi all,
>> when I used the Hive interpreter I could send several queries in
>> parallel. Now in Zeppelin 0.6 Hive Interpreter is merged into JDBC (which
>> is very good) but I can not execute concurrent Hive queries (which is not
>> so good).
>> How can I run concurrent queries to Hive using JDBC interpreter now in
>> Zeppelin 0.6?
>>
>> Regards,
>> Boris
>>
>
>
