Skip to content
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

Add Cassandra Scaler doc #452

Closed

Conversation

nilayasiktoprak
Copy link
Contributor

@nilayasiktoprak nilayasiktoprak commented May 21, 2021

Signed-off-by: nilayasiktoprak [email protected]

This PR adds documentation for Cassandra Scaler.

Relates to kedacore/keda#1841

Checklist

  • Commits are signed with Developer Certificate of Origin (DCO)
  • A PR is opened to update the documentation on our docs repo

Signed-off-by: nilayasiktoprak <[email protected]>
Comment on lines 26 to 27
authenticationRef:
name: keda-trigger-auth-cassandra-secret
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be left out here

Suggested change
authenticationRef:
name: keda-trigger-auth-cassandra-secret

- `username` - The username credential for connecting to the Cassandra instance.
- `clusterIPAddress` - The IP address or the host name of the Cassandra instance, with port number (optional).
- `consistency` - Configuration for a session or per individual read or write operation.
- `protoVersion` - CQL Binary Protocol.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about using protocolVersion?

Suggested change
- `protoVersion` - CQL Binary Protocol.
- `protocolVersion` - CQL Binary Protocol.


- `username` - The username credential for connecting to the Cassandra instance.
- `clusterIPAddress` - The IP address or the host name of the Cassandra instance, with port number (optional).
- `consistency` - Configuration for a session or per individual read or write operation.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe leave this out since we don't do writes?

Suggested change
- `consistency` - Configuration for a session or per individual read or write operation.
- `consistency` - Configuration for a session or per individual read operation.

**Parameter list:**

- `username` - The username credential for connecting to the Cassandra instance.
- `clusterIPAddress` - The IP address or the host name of the Cassandra instance, with port number (optional).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@zroubalik We had a scaler where we support full name and name + port separately, do you recall where we changed this? We might want to align here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe that it might be MSSQL scaler since the port is indicated as optional in the doc here: https://github.com/kedacore/keda-docs/blob/master/content/docs/2.3/scalers/mssql.md
So you mean that we should also support port as optional, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe that it might be MSSQL scaler since the port is indicated as optional in the doc here: https://github.com/kedacore/keda-docs/blob/master/content/docs/2.3/scalers/mssql.md
So you mean that we should also support port as optional, right?

Is this right? @tomkerkhove

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd love to align this indeed, what do you think @zroubalik ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I'd prefer to have the ability to specify the port in an optional field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants