flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aljoscha <...@git.apache.org>
Subject [GitHub] flink issue #4891: [FLINK-7669] Always load Flink classes via parent ClassLo...
Date Tue, 24 Oct 2017 09:25:52 GMT
Github user aljoscha commented on the issue:

    https://github.com/apache/flink/pull/4891
  
    Thanks for the reviews, @zentol and @StephanEwen?
    
    @StephanEwen Regarding your last two comments, it would be nice if the `ConfigOption`
itself did the parsing, i.e. if I could have a `ConfigOption<String, String[]>` or some
such that parses a string to a list of strings and deals with all exceptions. Same would be
true for the resolve order, where I would like to have `ConfigOption<String, ResolveOrder>`
and it internally does the enum parsing. As it is now I have to do the parsing and exception
handling in all places where the config is used. What do you think?
    
    Regarding the list of parent-first patterns, `javax.annotation` I can see, but where do
loggers bleed through the API?


---

Mime
View raw message