> 在 2021年1月26日,下午4:29,贺斌 <[email protected]> 写道:
> 
> As a DS user ,I don't want to see some confusing names. Often causes a lot of 
> problems.
> 
> 
> On 2021/01/20 02:31:17, Gang Li <[email protected]> wrote: 
>> I think may be I didn’t express clearly,`As a user` I means it’s only just 
>> my personal opinion as a user.
>> Welecome more users and developers to discuss.
>> 
>> Best Regards
>> 
>> ------------------------------------------------------
>> DolphinScheduler(Incubator) PPMC
>> Gang Li 李岗
>> 
>> [email protected]
>> 
>> 发件人: leon bao<mailto:[email protected]>
>> 发送时间: 2021年1月20日 0:09
>> 收件人: dev<mailto:[email protected]>
>> 主题: Re: [DISCUSS] Whether need to support case-sensitive when create 
>> resource and so on?
>> 
>> - As a user, I don't think users wish to define two different resources
>> with Shell_A and shell_a
>> 
>> There may be some other people want "Shell_A" is different with "shell_a".
>> Anyway, you can't imagine what users want, but you can say : "The system
>> donot support your requirement."
>> On the other hand, i think we can support this feature because it does not
>> look like a bad thing.
>> 
>> 
>> Gang Li <[email protected]> 于2021年1月19日周二 下午10:21写道:
>> 
>>> Background
>>> As the issue [1] shows,it will be appeared when you use mysql database.
>>> If you need to create a resource with name `Shell_A`,and if the resource
>>> which name is `shell_a` has been exsit,it will be created failure.
>>> 
>>> What need to discuss
>>> Whether need to support case-sensitive when create resource and so on?
>>> 
>>> As a user, I don't think users wish to define two different resources with
>>> Shell_A and shell_a.
>>> Feel free to discuss and give you suggestion,thx.
>>> 
>>> 
>>> [1] https://github.com/apache/incubator-dolphinscheduler/issues/2443
>>> 
>>> 
>>> Best Regards
>>> 
>>> ------------------------------------------------------
>>> DolphinScheduler(Incubator) PPMC
>>> Gang Li 李岗
>>> 
>>> [email protected]
>>> 
>>> 
>> 
>> --
>> DolphinScheduler(Incubator)  PPMC
>> BaoLiang 鲍亮
>> [email protected]
>> 

Reply via email to