Github user gaborgsomogyi commented on the issue:
https://github.com/apache/spark/pull/21455
Sounds weird. The topic names are available when the streaming app
submitted. Why this can't be reused? Second option is reflection as jerryshao
suggested.
---
Github user merlintang commented on the issue:
https://github.com/apache/spark/pull/21455
@gabor. These fields are important for us the understand the spark kafka
streaming data like the topic name. we can use these information to track
the system status.
On Tue, Jun
Github user gaborgsomogyi commented on the issue:
https://github.com/apache/spark/pull/21455
Why is it required at all? Making things visible without proper reason is
not a good idea.
---
-
To unsubscribe, e-mail:
Github user merlintang commented on the issue:
https://github.com/apache/spark/pull/21455
@jerryshao Actually, we can not use reflection to get this field
information.
---
-
To unsubscribe, e-mail:
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/21455
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/21455
Simply making these fields publicly accessible seems a little weird from
Spark's side. Maybe we can use reflection instead.
---
Github user merlintang commented on the issue:
https://github.com/apache/spark/pull/21455
@jerryshao can you review this minor update ?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/21455
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/21455
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
