Not the best idea but you can open another listener that is not SASL
enabled until they patch is released.
On Tue, Jul 31, 2018 at 8:17 AM, Pierre Coquentin <
pierre.coquen...@gmail.com> wrote:
> thanks, too bad :(
>
> On Tue, Jul 31, 2018 at 4:44 PM Gabriele Paggi
> wrote:
>
> > Hi Pierre,
> >
thanks, too bad :(
On Tue, Jul 31, 2018 at 4:44 PM Gabriele Paggi
wrote:
> Hi Pierre,
>
> Indeed, it doesn't support SASL_SSL.
> The issue is being worked on here:
> https://issues.apache.org/jira/browse/KAFKA-5235
>
> On Tue, Jul 31, 2018 at 2:19 PM Pierre Coquentin <
> pierre.coquen...@gmail.c
Hi Pierre,
Indeed, it doesn't support SASL_SSL.
The issue is being worked on here:
https://issues.apache.org/jira/browse/KAFKA-5235
On Tue, Jul 31, 2018 at 2:19 PM Pierre Coquentin
wrote:
> Hi
>
> Thanks for the answer but GetOffsetShell doesn't work with SSL and SASL
> enabled. It doesn't seem
Hi
Thanks for the answer but GetOffsetShell doesn't work with SSL and SASL
enabled. It doesn't seem possible to provide the consumer.config like we do
for kafka-console-consumer.sh.
On Tue, Jul 31, 2018 at 12:19 PM Gabriele Paggi
wrote:
> Hi Pierre,
>
> You can use kafka.tools.GetOffsetShell, w
Hi Pierre,
You can use kafka.tools.GetOffsetShell, which will return the earliest
offset for each partition in a given topic.
If you want to see the latest available ones, change "--time -2" with
"--time -1"
gpaggi@kafkalog001:~$ kafka-run-class.sh kafka.tools.GetOffsetShell
--broker-list $(hostn
Hi
How do we get the starting offset of a partition from a topic when we have
a retention policy configured?
I've checked in shell script kafka-topic.sh or kafka-console-consumer.sh
but found nothing so far. Do we have to implement our own solution to get
this information?
It could be nice in kafk