Consume Cassandra Heuristics and Generate CQL Data - #1795

@gonzalotguerrero please fix the merge conflicts

Hi @arcuri82! I have a few questions regarding your comments:

isn't this name confusing? as you are loading all initializing actions, not just for Cassandra

I understand it might be confusing, but I'd written it like that because it's the way it's written for the other DBs. Would you still like me to change it to a more generic name?

shouldn't have a @DependsOnTrueFor for extractSqlExecutionInfo ?

I'm having some trouble understanding this question. I don't see the other databases' attributes having this @DependsOnTrueFor, could you please provide more clarification as to why it would be necessary for the ones regarding Cassandra?

Thanks!

Hi @gonzalotguerrero , I think that what @arcuri82 probably meant was extractCassandraExecutionInfo

Hi @gonzalotguerrero , I think that what @arcuri82 probably meant was extractCassandraExecutionInfo

Hi @jgaleotti! I think so too, my question was more aimed at the fact that this @DependsOnTrueFor was not present for the other DBs (with their respective extractXXExecutionInfo attribute), but I just saw that Andrés recently added it for Neo4j. I'll get to adding it for Cassandra as well.

hi @gonzalotguerrero
thx, name is confusing, but, indeed, other DBs do the same. keep consistent names. i might refactor it in future for all DBs.

for @DependsOnTrueFor yes, that was not something done for all DBs (or all parameters that might need it). we can just add it for new parameters. In future I might review all existing params, and add it where needed

@gonzalotguerrero there is one merge conflict that needs to be fixed

@arcuri82 done! fixed merge conflicts + restored oldCassandraDbActions val name

I'll update the other branches to fix the conflicts as well