Nicoretti commented on issue #16541:
URL: https://github.com/apache/superset/issues/16541#issuecomment-1121107710

   ### Hi all, 
   (@ApfelPresse, @lkwg82, @betodealmeida, @hughhhh)
   
   
   I am the new maintainer of the 
[sqlalchemy-exasol](https://github.com/exasol/sqlalchemy-exasol) which is used 
in `apache-superset`.
   
   A colleague of mine (@tkilias) and I started digging a bit into this issue, 
to ensure this is not caused by 
[sqlalchemy-exasol](https://github.com/exasol/sqlalchemy-exasol).
   As of now, it is still not a 100% clear to us what the root cause is, but it 
surely looks like 
[sqlalchemy-exasol](https://github.com/exasol/sqlalchemy-exasol) is part of the 
problem.
   
   While trying to reproduce and analyzing the issue, we could figure out the 
following things:
   
   * The currently pinned version (`>=2.1.0, <2.2.0`) of `sqlalchemy-exasol` in 
the `setup.py` does not to work properly for adding any datasets with exasol.
   * The following combination of versions seem to work properly for adding 
datasets with exasol.
   
       ```
       apache-superset==1.5.0[exasol]
       sqlalchemy-exasol==2.0.10
       ```
       
       @ApfelPresse from what I could see it also works for your view based 
scenario.
       (Can you validate, that it is working for your scenario too?)
   
   * All version of `sqlalchemy-exasol > 2.0.10`, seem to have an issue when 
trying to add datasets from exasol.
   
       Until we can identify the root cause of this, it would make sense to:
       * Pin the `sqlalchemy-exasol` dependency to the version `2.0.10`
       * Document it as known issue
   
       I am happy to create a PR with those changes, if you think, this is 
reasonable from the `apache-superset` project point of view.
   
      @lkwg82, @betodealmeida, @hughhhh would you want me to also create a 
tracking issue for this in the `apache-superset` project?
   
   
   I hope this helps.
   
   best
   Nico
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to