Difference between revisions of "Trove/Blueprints/vertica-db-support"

Revision as of 09:41, 24 April 2014

Description

Include vertica analytical database in trove datastores.

Use Case Requirements

While the specific details of each datastore need to be investigated against this list, these are seen as the use-cases that would motivate the replication feature:

A. TEST HEADING

1. bullet 1
2. bullet 2

Scope

Implement all sections of Use Case Requirements.

Impacts

This change would impact all components of Trove.

Configuration

There should be no changes to configuration files required.

Database

• Does this impact any existing tables? If so, which ones?
• Are the changes forward and backward compatible?
• Be sure to include the expected migration process

Public API

• Does this change any API that an end-user has access to?
• Are there any exceptions in terms of consistency with other APIs?

The addition of a replication feature would required changes to the trove command and corresponding APIs. At a minimum, there would need to be APIs to add a slave to a master, and to remove a slave from a master. Additionally, there may be changes to how a potential master site is created.

Internal API

• Does this change any internal messages between API and Task Manager or Task Manager to Guest

There would be API changes at every level to support replication.

Guest Agent

• Does this change behavior on the Guest Agent? If so, is it backwards compatible with API and Task Manager?

The guest agent would require support for the new replication operations, but backward compatibility should be maintained.