|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [mojo-dev] [jira] (MCASSANDRA-31) Enable User to s... Lorcan Coyle (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-31) Enable User... Matthew Adams (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-31) Enable User... Lorcan Coyle (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-31) Enable User... Matthew Adams (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-31) Enable User... Lorcan Coyle (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-31) Enable User... Lorcan Coyle (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-31) Enable User... Lorcan Coyle (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-31) Enable User... Lorcan Coyle (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-31) Enable User... Lorcan Coyle (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-31) Enable User... Mikhail Mazursky (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-31) Enable User... Olivier Lamy (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-31) Enable User... Olivier Lamy (JIRA)

Yes, you can workaround but it's not as usable/configurable. I think the proposed solution is more consistent with the way other ports are configurable.
I thought about adding code to allow start_native_transport to be set/unset but my preference was to have it set by default in the cassandra.yaml file and not expose the setting - it's less likely to need to be customised. My reasoning (fwiw) was that as the community moves towards CQL they will be expecting start_native_transport to be set by default and will be unlikely to want/need to unset it. That said, I'm happy to produce a new patch enabling that to be customised along with native_transport_port.