Hi Charles, I'm not sure that it can be addressed in Drill only.
Kind regards, Volodymyr Vysotskyi On Thu, Jun 25, 2020 at 5:10 AM Charles Givre <cgi...@gmail.com> wrote: > Hi Ted, > That probably would solve the issue for the user. However what's happening > is that certain JDBC DBs (Oracle) are returning data types that Drill does > not support and the queries are failing with a validation error. IMHO, > there should be some way to either tell Drill that this weird field is a > specific datatype or something so that the user can access the data. > It seemed as if Vova proposed a solution to Calcite but it was never > adopted. I'm wondering if there's some way that we can either extend that > class, or somehow catch the exception which is being thrown and fix the > issue. > Best, > -- C > > > > > On Jun 24, 2020, at 6:20 PM, Ted Dunning <ted.dunn...@gmail.com> wrote: > > > > Charles, > > > > Do you think that suggesting using a non-materialized view would help in > > this case? > > > > On Wed, Jun 24, 2020 at 2:31 PM Charles Givre <cgi...@gmail.com> wrote: > > > >> Hi Vova, > >> I have a Calcite question for you. I’m helping someone debug an issue > >> they’re having connecting Drill to an OracleDB and they’re running into > the > >> issue you reported here: > >> https://issues.apache.org/jira/browse/CALCITE-3533 < > >> https://issues.apache.org/jira/browse/CALCITE-3533> > >> > >> I’m wondering if there’s a way that we could fix this on the Drill side > >> since it doesn’t look like Calcite is going to fix this. What do you > think? > >> Best, > >> — C > >
