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

revert the druid name and add it to fact name in slices endpoint #541

Merged
merged 1 commit into from
Sep 25, 2017

Conversation

asifmansoora
Copy link
Collaborator

Reverting this PR #491 so that the name still points to apiName and added factName which points to druidName

@asifmansoora asifmansoora force-pushed the reverting-druid-name-on-slices-servlet branch from 0241854 to 33a72a8 Compare September 22, 2017 20:14
@asifmansoora asifmansoora force-pushed the reverting-druid-name-on-slices-servlet branch from 33a72a8 to 2e21a8a Compare September 22, 2017 21:02
CHANGELOG.md Outdated
@@ -168,6 +168,9 @@ Current

### Removed:

- [Reverted the druid name change in slices endpoint instead added to factName](https://github.com/yahoo/fili/pull/541)
* Reverting this PR #491 so that the name still points to apiName and added factName which points to druidName.
Copy link
Contributor

@QubitPi QubitPi Sep 25, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding link to #491 makes it better
In addition, it makes more sense to talk about the reason for this roll back as well as factName

@@ -179,7 +179,8 @@ protected SlicesApiRequest() {
Column key = e.getKey();
if (key instanceof DimensionColumn) {
Dimension dimension = ((DimensionColumn) key).getDimension();
row.put("name", table.getPhysicalColumnName(dimension.getApiName()));
row.put("name", dimension.getApiName());
row.put("factName", table.getPhysicalColumnName(dimension.getApiName()));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dimension.getApiName() to a variable since it's used twice

if (it.key instanceof DimensionColumn) {
row["uri"] = uri + it.key.name
row["factName"] = table.getPhysicalColumnName(it.key.name)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious, why are we putting this inside a conditional?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because factName was valid only for dimension rows

Copy link
Contributor

@QubitPi QubitPi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo. Otherwise, looks good to me

CHANGELOG.md Outdated
@@ -172,7 +172,9 @@ Current
### Removed:

- [Reverted the druid name change in slices endpoint instead added to factName](https://github.com/yahoo/fili/pull/541)
* Reverting this PR #491 so that the name still points to apiName and added factName which points to druidName.
* Reverting the PR-419(https://github.com/yahoo/fili/pull/419) so that the name still points to apiName and added factName which points to druidName.
`name` was not valid for cases when its a Lookup dimension because it was pointing to the base dimension name , so reverted that change and added
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

its -> it is

@asifmansoora asifmansoora force-pushed the reverting-druid-name-on-slices-servlet branch from 6645068 to 06bfa3d Compare September 25, 2017 16:34
@asifmansoora asifmansoora merged commit 9be16ef into master Sep 25, 2017
@asifmansoora asifmansoora deleted the reverting-druid-name-on-slices-servlet branch September 25, 2017 16:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants