Skip to content
This repository has been archived by the owner on Sep 12, 2024. It is now read-only.

Add SAP HANA connector #960

Open
nico-hernandez opened this issue May 19, 2022 · 1 comment · May be fixed by #961
Open

Add SAP HANA connector #960

nico-hernandez opened this issue May 19, 2022 · 1 comment · May be fixed by #961
Labels
🔗 connectors DB, DW & third party connectors

Comments

@nico-hernandez
Copy link

nico-hernandez commented May 19, 2022

Tell us about the problem you're trying to solve

I want to connect Chaos Genius to a SAP HANA On-premise database. Many of the main metrics watched by our company are stored in on-premise database, particularly in SAP HANA On-Premise Database. Our managers are looking for detecting anomalies in business metrics. For instance: an anomaly in sales, under some asumptions and context, could trigger an alert of out-of-sotck on shelf.

Describe the solution you'd like

Connector to SAP HANA On-Premise database.

Describe alternatives you've considered

In Python, for instance, there is SQL Alchemy,, which supports HANA on-premise, https://github.com/SAP/sqlalchemy-hana.

Additional context

Consider that our database is multi-tenant.

@github-actions
Copy link

Hello there, thanks for opening your first issue. We welcome you to the community!

@Samyak2 Samyak2 added the 🔗 connectors DB, DW & third party connectors label May 20, 2022
@Samyak2 Samyak2 added this to the v0.8.0 milestone May 20, 2022
Samyak2 added a commit that referenced this issue May 23, 2022
Closes #960

TODO:
- Consider renaming the connector to `HANA` or `SAP HANA` since `Hana`
  isn't correct (it's an abbreviation).
@Samyak2 Samyak2 linked a pull request May 23, 2022 that will close this issue
3 tasks
@Samyak2 Samyak2 removed this from the v0.8.0 milestone Jun 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🔗 connectors DB, DW & third party connectors
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants