[Maria-discuss] CentOS7 Cassandra
Can someone clarify the status of Cassandra in CentOS7? It appears to have been available in 6, but not in 7.
On 1 Feb 2017, at 16:40, Ian Gilfillan <ian@mariadb.org> wrote:
Can someone clarify the status of Cassandra in CentOS7? It appears to have been available in 6, but not in 7.
I think the CassandraSE is deprecated. It probably is available in 6, but not 7, and I can’t imagine why it would be recommended for use, since you have to use it with an old release of Cassandra that is probably unsupported anymore These pages really should be archived - https://mariadb.com/kb/en/mariadb/cassandra/ with a reference to https://jira.mariadb.org/browse/MDEV-4695 And maybe closing some bugs as wontfix makes sense as well: https://jira.mariadb.org/browse/MDEV-534 https://jira.mariadb.org/browse/MDEV-6416 https://jira.mariadb.org/browse/MDEV-8947 https://jira.mariadb.org/browse/MDEV-10129 https://jira.mariadb.org/browse/MDEV-4631 https://jira.mariadb.org/browse/MDEV-7756 -- Colin Charles, http://bytebot.net/blog/ twitter: @bytebot | skype: colincharles "First they ignore you, then they laugh at you, then they fight you, then you win." -- Mohandas Gandhi
Am 01.02.2017 um 10:25 schrieb Colin Charles:
On 1 Feb 2017, at 16:40, Ian Gilfillan <ian@mariadb.org> wrote:
Can someone clarify the status of Cassandra in CentOS7? It appears to have been available in 6, but not in 7.
I think the CassandraSE is deprecated. It probably is available in 6, but not 7, and I can’t imagine why it would be recommended for use, since you have to use it with an old release of Cassandra that is probably unsupported anymore
maybe it should be re-considered add each and every stroage engine to MariaDB, especially when it relies on 3rd parties to keep it useable and in the worst case access your data at all becomes a problem in future updates not fixable by "mysql_upgrade" -DPLUGIN_ARCHIVE=NO \ -DPLUGIN_BLACKHOLE=NO \ -DPLUGIN_CASSANDRA=NO \ -DPLUGIN_CONNECT=NO \ -DPLUGIN_EXAMPLE=NO \ -DPLUGIN_FEDERATED=NO \ -DPLUGIN_FEDERATEDX=NO \ -DPLUGIN_FEEDBACK=NO \ -DPLUGIN_INNODB=NO \ -DPLUGIN_MROONGA=NO \ -DPLUGIN_MYISAMMRG=NO \ -DPLUGIN_OQGRAPH=NO \ -DPLUGIN_PARTITION=NO \ -DPLUGIN_PERFSCHEMA=NO \ -DPLUGIN_SEMISYNC=NO \ -DPLUGIN_SEQUENCE=NO \ -DPLUGIN_SPHINX=NO \ -DPLUGIN_SPIDER=NO \ -DPLUGIN_TOKUDB=NO \ -DWITHOUT_DYNAMIC_PLUGINS=ON \ that's to make the build faster, the memory footprint of the server lower and to make sure nobody ever will write code which uses exotic features making it unmaintainable in a few years or break it with the next mariadb version while MyISAM and XtraDB are mature for many years
On 2/1/2017 12:01 PM, Reindl Harald wrote:
Am 01.02.2017 um 10:25 schrieb Colin Charles:
On 1 Feb 2017, at 16:40, Ian Gilfillan <ian@mariadb.org> wrote:
Can someone clarify the status of Cassandra in CentOS7? It appears to have been available in 6, but not in 7.
I think the CassandraSE is deprecated. It probably is available in 6, but not 7, and I can’t imagine why it would be recommended for use, since you have to use it with an old release of Cassandra that is probably unsupported anymore
maybe it should be re-considered add each and every stroage engine to MariaDB, especially when it relies on 3rd parties to keep it useable and in the worst case access your data at all becomes a problem in future updates not fixable by "mysql_upgrade"
-DPLUGIN_ARCHIVE=NO \ -DPLUGIN_BLACKHOLE=NO \ -DPLUGIN_CASSANDRA=NO \ -DPLUGIN_CONNECT=NO \ -DPLUGIN_EXAMPLE=NO \ -DPLUGIN_FEDERATED=NO \ -DPLUGIN_FEDERATEDX=NO \ -DPLUGIN_FEEDBACK=NO \ -DPLUGIN_INNODB=NO \ -DPLUGIN_MROONGA=NO \ -DPLUGIN_MYISAMMRG=NO \ -DPLUGIN_OQGRAPH=NO \ -DPLUGIN_PARTITION=NO \ -DPLUGIN_PERFSCHEMA=NO \ -DPLUGIN_SEMISYNC=NO \ -DPLUGIN_SEQUENCE=NO \ -DPLUGIN_SPHINX=NO \ -DPLUGIN_SPIDER=NO \ -DPLUGIN_TOKUDB=NO \ -DWITHOUT_DYNAMIC_PLUGINS=ON \
You could just have used -DWITHOUT_DYNAMIC_PLUGINS=ON, to the same effect, but with a single CMake parameter rather than 20
that's to make the build faster, the memory footprint of the server lower and to make sure nobody ever will write code which uses exotic features making it unmaintainable in a few years or break it with the next mariadb version while MyISAM and XtraDB are mature for many years
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Am 01.02.2017 um 12:23 schrieb Vladislav Vaintroub:
On 2/1/2017 12:01 PM, Reindl Harald wrote:
Am 01.02.2017 um 10:25 schrieb Colin Charles:
On 1 Feb 2017, at 16:40, Ian Gilfillan <ian@mariadb.org> wrote:
Can someone clarify the status of Cassandra in CentOS7? It appears to have been available in 6, but not in 7.
I think the CassandraSE is deprecated. It probably is available in 6, but not 7, and I can’t imagine why it would be recommended for use, since you have to use it with an old release of Cassandra that is probably unsupported anymore
maybe it should be re-considered add each and every stroage engine to MariaDB, especially when it relies on 3rd parties to keep it useable and in the worst case access your data at all becomes a problem in future updates not fixable by "mysql_upgrade"
-DPLUGIN_ARCHIVE=NO \ -DPLUGIN_BLACKHOLE=NO \ -DPLUGIN_CASSANDRA=NO \ -DPLUGIN_CONNECT=NO \ -DPLUGIN_EXAMPLE=NO \ -DPLUGIN_FEDERATED=NO \ -DPLUGIN_FEDERATEDX=NO \ -DPLUGIN_FEEDBACK=NO \ -DPLUGIN_INNODB=NO \ -DPLUGIN_MROONGA=NO \ -DPLUGIN_MYISAMMRG=NO \ -DPLUGIN_OQGRAPH=NO \ -DPLUGIN_PARTITION=NO \ -DPLUGIN_PERFSCHEMA=NO \ -DPLUGIN_SEMISYNC=NO \ -DPLUGIN_SEQUENCE=NO \ -DPLUGIN_SPHINX=NO \ -DPLUGIN_SPIDER=NO \ -DPLUGIN_TOKUDB=NO \ -DWITHOUT_DYNAMIC_PLUGINS=ON \
You could just have used -DWITHOUT_DYNAMIC_PLUGINS=ON, to the same effect, but with a single CMake parameter rather than 20
if it would be that clear what is considered as dynamic or not and cmake would be that consistent and had something relieable than ./configure currently it's a wild mix of ENABLE (and even ENABLED), WITH, WITHOUT -DENABLED_PROFILING=OFF \ -DENABLE_DTRACE=OFF \ with 10.0.x FEDERATED was built with -DWITHOUT_DYNAMIC_PLUGINS=ON and in 10.1.x not - god save you when you disabled unwanted things in my.cf and in the next build it is skipped as it should be and the config option is no lonmger known so better be as explicit as possible.....
On Wed, Feb 01, 2017 at 05:25:37PM +0800, Colin Charles wrote:
On 1 Feb 2017, at 16:40, Ian Gilfillan <ian@mariadb.org> wrote:
Can someone clarify the status of Cassandra in CentOS7? It appears to have been available in 6, but not in 7.
I think the CassandraSE is deprecated. It probably is available in 6, but not 7, and I can’t imagine why it would be recommended for use, since you have to use it with an old release of Cassandra that is probably unsupported anymore
These pages really should be archived - https://mariadb.com/kb/en/mariadb/cassandra/ with a reference to https://jira.mariadb.org/browse/MDEV-4695
And maybe closing some bugs as wontfix makes sense as well: https://jira.mariadb.org/browse/MDEV-534 https://jira.mariadb.org/browse/MDEV-6416 https://jira.mariadb.org/browse/MDEV-8947 https://jira.mariadb.org/browse/MDEV-10129 https://jira.mariadb.org/browse/MDEV-4631
Yes. Closed these, thanks for the list.
https://jira.mariadb.org/browse/MDEV-7756 This one is actually about plugin variables, not just cassandra, so left it open.
-- Colin Charles, http://bytebot.net/blog/ twitter: @bytebot | skype: colincharles "First they ignore you, then they laugh at you, then they fight you, then you win." -- Mohandas Gandhi
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
-- BR Sergei -- Sergei Petrunia, Software Developer MariaDB Corporation | Skype: sergefp | Blog: http://s.petrunia.net/blog
participants (5)
-
Colin Charles -
Ian Gilfillan -
Reindl Harald -
Sergey Petrunia -
Vladislav Vaintroub