-
Notifications
You must be signed in to change notification settings - Fork 37
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
kafka-value-parser #29
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -224,23 +224,23 @@ | |
} | ||
|
||
# KAFKA | ||
{ | ||
name: tag7 | ||
type: { | ||
source: kafka | ||
sink: client | ||
} | ||
service: "kafka.service.address" | ||
topic: "topic-name" | ||
fields: [kafka-field-0, kafka-field-1, kafka-field-2] | ||
nebula.fields: [nebula-field-0, nebula-field-1, nebula-field-2] | ||
vertex: { | ||
field: kafka-field-0 | ||
} | ||
partition: 10 | ||
batch: 10 | ||
interval.seconds: 10 | ||
} | ||
# { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. please roll back these changes There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. A new check is added in the config parse that an exception would be throw if any other config define after kafka, see Config.scala. However, there is two kafka defined in the application.conf. If I don't comment this section, the test would not pass. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ok, I'll split the config of Kafka out and use a single config file for Kafka later. |
||
# name: tag7 | ||
# type: { | ||
# source: kafka | ||
# sink: client | ||
# } | ||
# service: "kafka.service.address" | ||
# topic: "topic-name" | ||
# fields: [kafka-field-0, kafka-field-1, kafka-field-2] | ||
# nebula.fields: [nebula-field-0, nebula-field-1, nebula-field-2] | ||
# vertex: { | ||
# field: kafka-field-0 | ||
# } | ||
# partition: 10 | ||
# batch: 10 | ||
# interval.seconds: 10 | ||
# } | ||
|
||
# MySql | ||
{ | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
don't we need alias the dataframe's column name to name in fields?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had ever print the col name which is the name of fields. It's workable in my machine..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, i tested it and the schema is the same with fields. Great work~