Hi Kevin,
Just a re-clarification: for Kafka 0.9 it would be “earliest”, & “smallest”
for the older Kafka 0.8.
I’m wondering whether or not it is reasonable to add a Flink-specific way
to set the consumer’s starting position to “earliest” and “latest”, without
respecting the external Kafka offset
Hi Kevin,
Was the same “group.id” used before?
What may be happening is that on startup of the consumer (not from failure
restore), any existing committed offset for the groupId in Kafka’s brokers
will be used as the starting point. The “auto.offset.reset” is only
respected when no committed offse
Hi Chen,
AFAIK, there currently isn’t any FLIP / JIRA / work currently for a
Cassandra state backend. I think it’ll definitely by interesting to have
one in Flink.
Regards,
Gordon
On July 25, 2016 at 10:24:32 AM, Chen Qin (qinnc...@gmail.com) wrote:
Hi there,
Is there any design docs or on g
sting message
key will have to still incur the unnecessary shuffle. Correct ? Or does
partitionCustom on the data stream somehow override the behaviour of
assignPartitions on the source ?
On Mon, Jun 20, 2016 at 11:01 AM, Tai Gordon wrote:
> Hi Michal,
>
> Whether or not the ext
Hi Michal,
Whether or not the external system's partitioning scheme is referenced when
assigning
partitions to the consumer parallel subtasks depends on the implementation
of each connector / source.
First, clarification on “co-partitioning": from your context I’m assuming
you’re referring to co-
