Affected Version
Since 0.17
Description
When dimensions is set in DruidInputSource, it doesn't respect dimensionsSpec. Instead, it uses dimensions in the inputSource. This results in a wrong schema of the reingested datasource. To fix this bug, InputRowSchema should be passed to DruidSegmentReader, so that it can use MapInputRowParser.parse() instead of creating MapBasedInputRow directly. Note that dimensionExclusions should be ignored when dimensions is set in DruidInputSource.
Affected Version
Since 0.17
Description
When
dimensionsis set inDruidInputSource, it doesn't respect dimensionsSpec. Instead, it usesdimensionsin the inputSource. This results in a wrong schema of the reingested datasource. To fix this bug,InputRowSchemashould be passed toDruidSegmentReader, so that it can useMapInputRowParser.parse()instead of creatingMapBasedInputRowdirectly. Note thatdimensionExclusionsshould be ignored whendimensionsis set inDruidInputSource.