[jira] [Created] (IGNITE-7402) Add ODBC security support
Blackfield created IGNITE-7402: -- Summary: Add ODBC security support Key: IGNITE-7402 URL: https://issues.apache.org/jira/browse/IGNITE-7402 Project: Ignite Issue Type: Improvement Components: odbc Affects Versions: 2.3 Reporter: Blackfield ODBC driver does not support username password to be passed to security plugin in. Please enable end user to provide user name and password. The DSN info on Windows is stored in registry as plain text. The password should NOT be stored as plain text (e.g. encrypted). See Ignite-6941 for the JDBC counter part. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-7029) Add an ability to provide multiple connection addresses for thin JDBC driver
[ https://issues.apache.org/jira/browse/IGNITE-7029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16269089#comment-16269089 ] Blackfield commented on IGNITE-7029: IGNITE-6942 covers the failover feature. This ticket asks for load balancing feature implemented as well. > Add an ability to provide multiple connection addresses for thin JDBC driver > > > Key: IGNITE-7029 > URL: https://issues.apache.org/jira/browse/IGNITE-7029 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Affects Versions: 2.3 >Reporter: Valentin Kulichenko > > Currently we allow only to provide one address when connecting via thin JDBC > driver. This has to issues: > * If node driver is connected to goes down, the driver stops working. > * Driver has to always go though the same node - this is a bottleneck. > As a simple solution we can allow to provide multiple addresses, like MySQL > does for example: > https://dev.mysql.com/doc/connector-j/5.1/en/connector-j-usagenotes-j2ee-concepts-managing-load-balanced-connections.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-7051) SQL Rename table support
Blackfield created IGNITE-7051: -- Summary: SQL Rename table support Key: IGNITE-7051 URL: https://issues.apache.org/jira/browse/IGNITE-7051 Project: Ignite Issue Type: Improvement Components: sql Affects Versions: 2.3 Reporter: Blackfield Use case was discussed at length here: http://apache-ignite-users.70518.x6.nabble.com/Continuous-update-Data-Grid-Cache-td2075.html#a17641 Currently, we have to load data to second table, the client then has to change their query to query this new table. Drop the old table. The latest suggestion in the above thread to "load new data set in the same cache and remove old entries once preloading is finished" is not feasible since for large table and table scan query (thus requires whole dataset to be loaded), it will take a while to load everything - thus increasing the downtime. Table rename support will reduce the downtime greatly. Ref: Postgresql and H2 syntax ALTER TABLE TmpTable RENAME TO Table1; Then, one would wrap it within transaction (It appears that this is slated for 2.4/2.5?) to drop old table, rename temp table to original table. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
