Skip to content

Separate hash/partition keys from range/sort keys #1018

@rfecher

Description

@rfecher

Currently the IndexStrategy is responsible for generating single keys and query ranges. DynamoDB and Cassandra require the partition portion of the key be separate from the sort key.

This issue should lend itself to a follow on issue that should also give the ability to appropriately track the portions of the key for good data density informed input splits for analytics. A continuous histogram should be maintained only on the isolated portion of the key that is meant to be well-sorted and range scanned (the SFC). A separate discrete histogram should be maintained for the partition/hash portion.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions