Tableau: Usage guide

[amotl]

About

Continue adding integration guides from the community forum.

Preview

• https://cratedb-guide--306.org.readthedocs.build/integrate/tableau/usage.html

References

• Consolidate Integration Guides I vs. II #102

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch tableau

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[amotl]

@surister: That's the original from Using CrateDB with Tableau. It should probably be considered outdated and be replaced or refer to the new connector's "Install" section instead?

[surister]

We could consider that yeah, even though using the jdbc connector might work fine for simple things.

[surister]

This is from the README right? Do you think it'd be better if I took this and expanded it a little bit, perhaps with some key screenshots and following the guide myself in my tableau installation?

[amotl]

Yeah, my intention was to just stage this patch and then humbly ask you to take over and cherry-pick / curate a good variant from your pen, probably based on the project's README and DEVELOP files. It's a good idea to include key screenshots at your disposal, please link to them so they not necessarily need to be physically included here. Thank you. 🙏

Using the jdbc connector might work fine for simple things.

If you want, you can retain the "basic setup" based on the PostgreSQL connector in a separate page, maybe usage-postgresql.md, if that makes sense, or just leave it on the same page within a bottom section.