You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@inlong.apache.org by "fuweng11 (via GitHub)" <gi...@apache.org> on 2023/04/03 02:26:02 UTC

[GitHub] [inlong] fuweng11 opened a new issue, #7760: [Bug][Manager] Parse fields failed for streamSink and InlongStream

fuweng11 opened a new issue, #7760:
URL: https://github.com/apache/inlong/issues/7760

   ### What happened
   
   Parse fields failed for streamSink and InlongStream.
   
   ### What you expected to happen
   
   Parse fields success for streamSink and InlongStream.
   
   ### How to reproduce
   
   Parse fields for streamSink and InlongStream.
   
   ### Environment
   
   _No response_
   
   ### InLong version
   
   master
   
   ### InLong Component
   
   InLong Manager
   
   ### Are you willing to submit PR?
   
   - [X] Yes, I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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: dev-unsubscribe@inlong.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [inlong] dockerzhang closed issue #7760: [Bug][Manager] Parse fields failed for streamSink and InlongStream

Posted by "dockerzhang (via GitHub)" <gi...@apache.org>.

dockerzhang closed issue #7760: [Bug][Manager] Parse fields failed for streamSink and InlongStream
URL: https://github.com/apache/inlong/issues/7760


-- 
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: dev-unsubscribe@inlong.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org