Skip to main content

Capabilities for SingleStore

Justin Stevenson
Updated

Capabilities for SingleStore

This section lists the of HVR when using 'SingleStore'. For more information about the pre-requisites, access privileges, and other configuration requirements, see .

Capture

HVR does not support changes from location on SingleStore.

Hub Database

HVR does not support Hub database on SingleStore.

Integrate

HVR supports the following capabilities on SingleStore:

  • changes into location (SingleStore version 7.1).
  • with /Burst (SingleStore version 7.1).
  • with /BurstCommitFrequency (SingleStore version 7.1).
  • Continuous integration ( without /Burst) (SingleStore version 7.1).
  • Action with /DuplicateRows for continuous integration (SingleStore version 7.1).
  • Action /SoftDelete (SingleStore version 7.1).
  • Bulk load requires a staging area ( /StagingDirectoryHvr) (SingleStore version 7.1).
  • Creation and update of HVR state tables (SingleStore version 7.1).

HVR does not support the following capabilities on SingleStore:

  • Continuous with /OnErrorSaveFailed (without /Burst).
  • Disable/enable database triggers during (/NoTriggerFiring).
  • with /DbProc.

Bi-directional Replication

HVR does not support Bi-directional Replication on SingleStore.

Refresh and Compare

HVR supports the following capabilities on SingleStore:

  • or from source location (SingleStore version 7.1).
  • into target location (SingleStore version 7.1).
  • Row-wise into target location (option -g) (SingleStore version 7.1).

Other Capabilities

HVR supports the following capabilities on SingleStore:

  • Both row store and column store tables can be created (SingleStore version 7.1).
  • Use distribution key for parallelizing changes within a table ( /DistributionKey) (SingleStore version 7.1).
  • Call database procedure dbproc during replication jobs (action /DbProc) (SingleStore version 7.1).
  • International table and column names where DBMS is not configured with UTF-8 encoding (SingleStore version 7.1).
  • Treat DBMS table names and columns as case sensitive if configured (action /CaseSensitiveNames defined) (SingleStore version 7.1).
  • Always treat DBMS table names and column names as case sensitive, even if not configured (action /CaseSensitiveNames not defined) (SingleStore version 7.1).
  • Always treat DBMS schema names case sensitive (SingleStore version 7.1).

HVR does not support the following capabilities on SingleStore:

  • Lossless binary float datatypes. No dataloss when transporting float values (because base 2 fractions are never converted to base 10).

Comments

0 comments

Please sign in to leave a comment.

Powered by Zendesk