-
Notifications
You must be signed in to change notification settings - Fork 96
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Implement dimension metadata to indicate storage strategy
- Loading branch information
Showing
10 changed files
with
144 additions
and
51 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
28 changes: 28 additions & 0 deletions
28
...core/src/main/java/com/yahoo/bard/webservice/data/dimension/metadata/StorageStrategy.java
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
// Copyright 2017 Yahoo Inc. | ||
// Licensed under the terms of the Apache license. Please see LICENSE.md file distributed with this work for terms. | ||
package com.yahoo.bard.webservice.data.dimension.metadata; | ||
|
||
/** | ||
* Allows clients to be notified if a dimension's values are browsable and searchable. | ||
* <p> | ||
* For the non-loaded dimensions(A "non-loaded dimension" is a fact based dimension, where we don't load any domain data | ||
* for it, but simply send queries directly to druid), we need to surface metadata to the UI. If there aren't dimension | ||
* values loaded, we can't validate when we build filters and you can't use the dimension values endpoint to browse | ||
* values. UI needs to know that a dimension isn't going to be validated and searched. The way that UI knows about this | ||
* is through this <tt>StorageStrategy</tt> | ||
*/ | ||
public enum StorageStrategy { | ||
/** | ||
* Loaded dimension. | ||
*/ | ||
LOADED, | ||
/** | ||
* Non-loaded dimension. | ||
*/ | ||
NONE; | ||
|
||
@Override | ||
public String toString() { | ||
return name(); | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.