suneet-s commented on pull request #11545: URL: https://github.com/apache/druid/pull/11545#issuecomment-893967172
> > @bananaaggle Do you think you could take a stab at fixing the web-console to use the inputFormat instead of the parser in a future change? I don't know a lot about front-end coding but that would be awesome for people to be able to use the UI instead of having to hand craft the ingestion spec. Thanks again for all your contributions! > > Actually, all data formats in core extension have been adapted to `inputformat`. Only one thrift contrib-extension does not have implementation which is in processing in [11360](https://github.com/apache/druid/pull/11360). So in next release, users won't meet this trouble because them can use `inputformat` to ingest data with all formats. If you mean we should support `parser` in UI, I think it's easy to change front-end code and I can do it. But Because `parser` will be deprecated, so it's not necessary supporting it in front-end(new users will not use it through UI if we change user guide). If you think it's necessary to fix it for some old users, I'm glad to make this change. I misunderstood when I wrote my last comment - I thought the web console was generating a deprecated parse spec when users selected protobuf, avro, etc. I agree with you that since the `parser` will be deprecated, it's not necessary to support it in the front-end. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
