You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a POC Vertica CE module. Vertica is a data warehouse using a columnar database but also supports standard SQL. The product itself is cloud-based but there is a docker-based 'community edition' version.
This module can successfully start the server and execute a test query. It does not yet support TLS, and I have no made no attempt to access it as a data warehouse.
Unfortunately, I didn't realize their definition of 'community edition' is much more restrictive than usual so that will need to be resolved before the module can be added. Anyone who can use this module should already have a broader license and can clearly benefit from this module - that should be an easy sell.
That leaves the question of ensuring we have a perpetual license that will let anyone, anywhere, build this module. I'll need to circle back to this.
I'll be submitting a POC PR for anyone who wants to see what I have so far.
The text was updated successfully, but these errors were encountered:
Hi @beargiles, the ideal workflow would be to raise an issue or discussion first, triage it and then raise the PR.
I think the blocker I see is how to test it ourselves. There is also another option, which is ask Vertica or OpenText to host the module. If we are not able to run the tests then we can not maintain the module.
Module
Core
Proposal
I have a POC Vertica CE module. Vertica is a data warehouse using a columnar database but also supports standard SQL. The product itself is cloud-based but there is a docker-based 'community edition' version.
This module can successfully start the server and execute a test query. It does not yet support TLS, and I have no made no attempt to access it as a data warehouse.
Unfortunately, I didn't realize their definition of 'community edition' is much more restrictive than usual so that will need to be resolved before the module can be added. Anyone who can use this module should already have a broader license and can clearly benefit from this module - that should be an easy sell.
That leaves the question of ensuring we have a perpetual license that will let anyone, anywhere, build this module. I'll need to circle back to this.
I'll be submitting a POC PR for anyone who wants to see what I have so far.
The text was updated successfully, but these errors were encountered: