You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to run one of the demos of Aiven's tiered storage implementation, but faced the following issue, when run the create_topic_by_size_ts make command:
Error: Could not find or load main class kafka.admin.TopicCommand
Caused by: java.lang.ClassNotFoundException: kafka.admin.TopicCommand
Under the hood the create_topic_by_size_ts command simply execs the /bin/kafka-topics script inside the Kafka with tiered storage container, that is based on the docker.io/aivenoy/kafka:3.7.0-2024-05-17 image. And if you run docker run --rm -it --entrypoint /bin/kafka-topics docker.io/aivenoy/kafka:3.7.0-2024-05-17 you will face the same issue.
After some investigation I found that the kafka.admin.TopicCommand class was moved to another package. Related changes (including renaming the full class name inside /bin/kafka-topics ) are also present in your fork, but for some reason not present in the docker image.
The text was updated successfully, but these errors were encountered:
@tigrulya-exe sorry for the long delay, this one slip through my notifications.
I guess this is not a problem anymore now that the demos are in a more recent version, right?
I tried to run one of the demos of Aiven's tiered storage implementation, but faced the following issue, when run the
create_topic_by_size_ts
make command:Under the hood the
create_topic_by_size_ts
command simply execs the/bin/kafka-topics
script inside the Kafka with tiered storage container, that is based on thedocker.io/aivenoy/kafka:3.7.0-2024-05-17
image. And if you rundocker run --rm -it --entrypoint /bin/kafka-topics docker.io/aivenoy/kafka:3.7.0-2024-05-17
you will face the same issue.After some investigation I found that the
kafka.admin.TopicCommand
class was moved to another package. Related changes (including renaming the full class name inside/bin/kafka-topics
) are also present in your fork, but for some reason not present in the docker image.The text was updated successfully, but these errors were encountered: