You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2021/07/05 12:29:11 UTC
[GitHub] [druid] smic-datalabs-von opened a new issue #11410: Zero metrics if data is from a druid inputSource
smic-datalabs-von opened a new issue #11410:
URL: https://github.com/apache/druid/issues/11410
I am encountering a problem that is similar to past closed issues: #10596 and #5277
I am using Druid 0.21.1
My problem is very similar with #10596. I am creating a new aggregated table from a Druid dataSource. I am converting some of the dimension columns into metric in order to rollup and make queries faster. This in turn makes all the rows in the new table have a value of zero in the metric columns.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
[GitHub] [druid] smic-datalabs-von commented on issue #11410: Zero metrics if data is from a druid inputSource
Posted by GitBox <gi...@apache.org>.
smic-datalabs-von commented on issue #11410:
URL: https://github.com/apache/druid/issues/11410#issuecomment-874127584
I already found a solution for this.
I actually found the solution in this [Druid User Group thread](https://groups.google.com/g/druid-user/c/2f-tjuo2bSQ/m/8RNqXET6AQAJ)
Basically, you have to indicate the target columns in the `metrics` key in `ioConfig`.
Something like this:
```json
"ioConfig": {
"type": "index_parallel",
"inputSource": {
"type": "druid",
"dataSource": "druid_ds",
"interval": "2019-01-07/2019-01-10",
"metrics": ["metric1", "metric2"] <-- THIS SHOULD BE THE TARGET COLUMNS
}
```
Do note that the target columns does not necessarily have to be metric columns in the originating dataSource. You just have to indicate it in order for the spec to get those columns for metrics processing.
I am leaving this issue open since this is an annoying bug and needs to be fixed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
[GitHub] [druid] smic-datalabs-von edited a comment on issue #11410: Zero metrics if data is from a druid inputSource
Posted by GitBox <gi...@apache.org>.
smic-datalabs-von edited a comment on issue #11410:
URL: https://github.com/apache/druid/issues/11410#issuecomment-874127584
I already found a solution for this.
I actually found the solution in this [Druid User Group thread](https://groups.google.com/g/druid-user/c/2f-tjuo2bSQ/m/8RNqXET6AQAJ)
Basically, you have to indicate the target columns in the `metrics` key in `ioConfig`.
Something like this:
```json
"ioConfig": {
"type": "index_parallel",
"inputSource": {
"type": "druid",
"dataSource": "druid_ds",
"interval": "2019-01-07/2019-01-10",
"metrics": ["metric1", "metric2"]
}
```
Where ` "metric1"` and `"metric2"` are your TARGET COLUMNS
The target columns does not necessarily have to be metric columns in the originating dataSource. Dimension columns are fine. You just have to indicate it in the `metrics` key under `ioConfig` in order for the ingestion process to get those columns for metrics processing.
I am leaving this issue open since this is an annoying bug and needs to be fixed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
[GitHub] [druid] smic-datalabs-von edited a comment on issue #11410: Zero metrics if data is from a druid inputSource
Posted by GitBox <gi...@apache.org>.
smic-datalabs-von edited a comment on issue #11410:
URL: https://github.com/apache/druid/issues/11410#issuecomment-874127584
I already found a solution for this.
I actually found the solution in this [Druid User Group thread](https://groups.google.com/g/druid-user/c/2f-tjuo2bSQ/m/8RNqXET6AQAJ)
Basically, you have to indicate the target columns in the `metrics` key in `ioConfig`.
Something like this:
```json
"ioConfig": {
"type": "index_parallel",
"inputSource": {
"type": "druid",
"dataSource": "druid_ds",
"interval": "2019-01-07/2019-01-10",
"metrics": ["metric1", "metric2"]
}
```
Where ` "metric1"` and `"metric2"` are your TARGET COLUMNS
The target columns does not necessarily have to be metric columns in the originating dataSource. Dimension columns are fine. You just have to indicate it in the `metrics` key under `ioConfig` in order for the ingestion process to get those columns for metrics processing.
I am leaving this issue open since this is an annoying bug and needs to be fixed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
[GitHub] [druid] smic-datalabs-von commented on issue #11410: Zero metrics if data is from a druid inputSource
Posted by GitBox <gi...@apache.org>.
smic-datalabs-von commented on issue #11410:
URL: https://github.com/apache/druid/issues/11410#issuecomment-874127584
I already found a solution for this.
I actually found the solution in this [Druid User Group thread](https://groups.google.com/g/druid-user/c/2f-tjuo2bSQ/m/8RNqXET6AQAJ)
Basically, you have to indicate the target columns in the `metrics` key in `ioConfig`.
Something like this:
```json
"ioConfig": {
"type": "index_parallel",
"inputSource": {
"type": "druid",
"dataSource": "druid_ds",
"interval": "2019-01-07/2019-01-10",
"metrics": ["metric1", "metric2"] <-- THIS SHOULD BE THE TARGET COLUMNS
}
```
Do note that the target columns does not necessarily have to be metric columns in the originating dataSource. You just have to indicate it in order for the spec to get those columns for metrics processing.
I am leaving this issue open since this is an annoying bug and needs to be fixed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org