Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draw up catalog.json format version 3 #31

Open
piroor opened this issue Dec 12, 2014 · 0 comments
Open

Draw up catalog.json format version 3 #31

piroor opened this issue Dec 12, 2014 · 0 comments

Comments

@piroor
Copy link
Contributor

piroor commented Dec 12, 2014

Known problems in v2 (should be fixed at version 3):

  • "replicas" appears in a dataset definition directly. It should be placed under "volume".

  • We cannot put replicas under a slice. (note: actually this can be done on the latest implementation for v2, but it is invalid as a v2 catalog.)

  • "volume" should be optional. If a slice doesn't have "volume", the slice itself should be parsed as a volume.
    Otherwise, we'll see deeply nested JSONs like: "dataset-volume-replicas-slices-slice-volume-replicas-..."

  • Replicas according to application by use. For example:

    • Replica 1: There is only one slice. This should be used for generic search.
    • Replica 2: There are time-sliced slices. This should be used for search with year.
    • Replica 3: There are category-sliced slices. This should be used for search with category.

    For these replicas, search requests should be delivered only for suitable replica for the use case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant