As verified the thing worked in my sandbox.
I'm running a 2.0 binary on a 1.6 metadata. The cube has override
properties:
"override_kylin_properties" : {
"kylin.job.mr.config.override.test.foo" : "barbar"
}
And the setting effectively reflects in MR job configuration in YARN web
GUI.
Still don't know why it didn't work in BioLearning's case. Suggest check
YARN GUI to verify the MR job configuration. Also this setting does not
affect Hive which is as designed.
Cheers
Yang
On Thu, May 4, 2017 at 1:53 PM, Li Yang <[email protected]> wrote:
> From code, it looks like the backward compatibility is already
> implemented. I'm doing a real test now.
>
> On Thu, May 4, 2017 at 1:24 PM, ShaoFeng Shi <[email protected]>
> wrote:
>
>> Which version are you running? I know v1.6 works okay, but when dev v2.0,
>> there is a rename for these property names, the prefix has been changed to "
>> kylin.engine.mr.config-override.". Please take a try, and we will update
>> the doc soon.
>>
>> 2017-05-03 23:04 GMT+08:00 ? ? <[email protected]>:
>>
>>> Hey,
>>>
>>>
>>> I tried to overwrite some mapred conf at cube level - Advanced Setting,
>>> but per configuration of mapred job in Job UI, they did not take effect.
>>> what is the wrong, or Kylin does not support to overwrite the conf items?
>>>
>>>
>>> "kylin.job.mr.config.override.mapreduce.reduce.cpu.vcores": "8",
>>> "kylin.job.mr.config.override.mapreduce.map.cpu.vcores": "8",
>>>
>>>
>>>
>>
>>
>> --
>> Best regards,
>>
>> Shaofeng Shi 史少锋
>>
>>
>
