-
Notifications
You must be signed in to change notification settings - Fork 601
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TabPy Roadmap #84
Comments
Would definitely like to know the roadmap. I think there are other enhancements needed in addition to clustering (see other Feature requests). I haven't heard much traffic on those requests either yet. |
very valid question, can you please add a roadmap for this project even if it's maintained by the community? |
Hi – I’m the new product manager at Tableau driving enhancements for advanced analytics and responsible for TabPy. I've been involved with TabPy for a while and it’s been great to see how the community has been using it to solve new challenges with Tableau. We’re always listening for your feedback on ways that we can improve external services to solve new problems and give you expanded functionality. Although TabPy is a community supported project, we have a few feature improvements planned for coming releases such as: As always, we’d love to hear your feedback on specific ideas or features that you’d like to see in the future. Don’t hesitate to contact me directly at [email protected] or continue the conversation here in github. |
One additional piece we are interested in gathering information on: would usability of TabPy be improved by the ability to return a table of data to Tableau instead of just a single column? If you have feedback or ideas on this or any topic please email me at [email protected]. |
This project is the current state of all the issues opened for TabPy - https://github.com/tableau/TabPy/projects/3. |
Hi, just wonder what the roadmap was for this project?
The reason that I ask is we're hoping to use this project to run python ML models to power Tableau dashboards, but it doesn't seem that friendly from an DevOps standpoint... the state.ini and query_objects/ are in a folder in a the site-packages, if we wanted to run multiple load baanced TabPy instances we would need to mount a shared disk to this directory etc. And state.ini is not exactly a robust database format :)
Do you guys have plans to make this project more robust, or it was only ever intended for running in single installation environments? Or perhaps something else is on the horizon for Tableau 2018.x that we should wait for?
The text was updated successfully, but these errors were encountered: