[
https://issues.apache.org/jira/browse/KNOX-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995306#comment-15995306
]
Rick Kellogg commented on KNOX-768:
-----------------------------------
To quote the Confluent documentation under Production Deployment(
http://docs.confluent.io/current/kafka-rest/docs/deployment.html#kafkarest-deployment):
You can also use an HTTP load balancer, but individual instances must still be
addressable to support the absolute URLs returned for use in consumer read and
offset commit operations.
Therefore it looks like producing messages via Knox to the Kafka REST Proxy
will be a straight pass-through, consuming them will be more involved s the
distinct URL endpoint must be used. The Kafka REST Proxy is stateful.
> Kafka REST Proxy API through Knox
> ----------------------------------
>
> Key: KNOX-768
> URL: https://issues.apache.org/jira/browse/KNOX-768
> Project: Apache Knox
> Issue Type: New Feature
> Affects Versions: 0.11.0
> Environment: All
> Reporter: Jeffrey E Rodriguez
> Assignee: Jeffrey E Rodriguez
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Kafka Rest Proxy ( as documented in Kafka REST Proxy )
> The Kafka REST Proxy provides a RESTful interface to a Kafka cluster. It
> makes it easy to produce and consume messages, view the state of the cluster,
> and perform administrative actions without using the native Kafka protocol or
> clients. Examples of use cases include reporting data to Kafka from any
> frontend app built in any language, ingesting messages into a stream
> processing framework that doesn’t yet support Kafka, and scripting
> administrative actions.
> This feature allow to call Kafka REST API through Knox.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
