-
-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FE: Is available to support property format in Kafka Connect? #699
Comments
Hi jx2lee! 👋 Welcome, and thank you for opening your first issue in the repo! Please wait for triaging by our maintainers. As development is carried out in our spare time, you can support us by sponsoring our activities or even funding the development of specific issues. If you plan to raise a PR for this issue, please take a look at our contributing guide. |
The Kafka Connect REST Interface only allows JSON messages. Could you clarify where can you post property files? Or is your request that the UI converts the property files to a JSON and publishes that? |
@yeikel Oh, I wrote the issue wrong.
I need the UI to convert the property files to JSON. I checked and the connect REST interface only accepts JSON, I'll fix issue body! --> TLDR; feature to convert property files a JSON |
Why? Who uses .properties if only json is supported? |
think that it is probably easier to use any of the online converters than to delegate this responsibility to the UI
Based on the comment above, it seems to be because they come from a tool that supports that |
Issue submitter TODO list
Is your proposal related to a problem?
I used to lenses-io connect-ui, this supported property format. but, I'm using kafka-ui, Not providing a property format was inconvenient.
Describe the feature you're interested in
I need to support property formatted in ui to convert json!
Describe alternatives you've considered
I wish there was above img, to select what i want to used. (maybe properties & json)
Version you're running
2956664
Additional context
No response
The text was updated successfully, but these errors were encountered: