Salamou alaikoum,

Sorry for taking so long man, I'm super busy these days working on a new
feature we are trying to add.

Anyway, I took a look at the JIRA and I'm not sure there is an easy answer
to your question, but if you want to verify the fix I think you just need
to reproduce the unit test that Jacques added as part of the fix. Let me
explain to you how it works:

- I attached a .json file to this email, you will use this as test data to
verify the fix
- you need to create a jdbc program that uses drill-jdbc-all jar file and
run a select * on this .json file. You should use the following method to
query the file:

https://gist.github.com/adeneche/230f671783aecca9db4d9cb51a4d656d

- Your program should run fine on master but fail on any version prior to
Jacques fix.

Let me know if this works for you

Ramadhan kareem


On Fri, Jun 17, 2016 at 5:55 AM, Khurram Faraaz <[email protected]>
wrote:

> Hi All,
>
> This should be an easy one to verify and close.
>
> In order to verify and mark jira DRILL-4291 as closed please confirm what
> are the classes that should be part of jdbc-all driver jar to return
> VarChar[]
>
> DRILL-4291 Ensure the jdbc-all driver jar includes *classes required *to
> return VarChar[]
>
> I can verify once I know the classnames to look for in jdbc-all driver jar
>
> Thanks,
> Khurram
>



-- 

Abdelhakim Deneche

Software Engineer

  <http://www.mapr.com/>


Now Available - Free Hadoop On-Demand Training
<http://www.mapr.com/training?utm_source=Email&utm_medium=Signature&utm_campaign=Free%20available>

Attachment: types.json
Description: application/json

Reply via email to