search

quantumquark / starschema-bigquery-jdbc

Automatically exported from code.google.com/p/starschema-bigquery-jdbc
0 stars 0 forks source link

Integer field should allow values of length Long #6

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
When storing a long integer within Big Query that exceeds the limitations of a 
java int but satisfies a long, querying this field in BigQuery web console 
shows the correct results, yet when executing the same query in Jasper using 
this jdbc connector the result is null, while all other data works.

Changing the type to String shows the value is populated as well. Unfortunately 
the limitation is that these fields must be of type Integer ( satisfying java 
long values ).

Original issue reported on code.google.com by gwhita...@arclight.com.au on 12 Aug 2013 at 4:46

GoogleCodeExporter commented 8 years ago 
Incorrectly diangosed required to be allocated against Bigquery Data Source 
instead of bigquery JDBC. see 
https://code.google.com/p/jaspersoft-bigquery-datasource/issues/detail?id=2&than
ks=2&ts=1376284633 for reposting of issue in correct location.

Original comment by gwhita...@arclight.com.au on 12 Aug 2013 at 5:17

GoogleCodeExporter commented 8 years ago 
It works in our connector.

Original comment by guni...@starschema.net on 23 Nov 2013 at 9:26