You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@pulsar.apache.org by Apache Pulsar Slack <ap...@gmail.com> on 2019/06/22 09:11:03 UTC
Slack digest for #general - 2019-06-22
2019-06-21 13:44:13 UTC - Alexandre DUVAL: Hi, what can be the reason that my topic has now a 404not found schema? I was using it without problem by a pulsar function I updated my pulsar function using pulsar-admin functions update and now the topic has no schema and when i try to upload the schema it's a timeout. :weary:
----
2019-06-21 13:52:46 UTC - Alexandre DUVAL:
----
2019-06-21 13:58:10 UTC - David Kjerrumgaard: @Alexandre DUVAL What changed inside the function (for the update) ? Did you use a different version Pulsar client or API?
----
2019-06-21 13:59:13 UTC - Alexandre DUVAL: Just a typo error during process. But this function was consuming two topics and only one is affected.
----
2019-06-21 13:59:35 UTC - Alexandre DUVAL: I updated it again to only one topic which has a schema and all is running
----
2019-06-21 14:01:10 UTC - Alexandre DUVAL: But cant consume the other one
----
2019-06-21 14:01:15 UTC - Alexandre DUVAL: :/
----
2019-06-21 14:03:09 UTC - David Kjerrumgaard: Can you consume from the topic using the CLI interface, i.e. `pulsar-client consume ...` ?
----
2019-06-21 14:03:26 UTC - David Kjerrumgaard: just as a sanity check
----
2019-06-21 14:11:28 UTC - Alexandre DUVAL: @David Kjerrumgaard yes i can
----
2019-06-21 14:19:16 UTC - David Kjerrumgaard: So, Topic A has a schema, and Topic B does not. Your function can consume from Topic A but not B?
----
2019-06-21 20:26:38 UTC - Sinan Bir: I'd like use JSON Web Token authentication with websocket api but I couldn't find any information about how to implement it. Currently I have written websocket client library in C#. I've added to request header "Authorization":"Bearer xxx" parameter and when I want to connect to server I got exception of
"18:28:10.271 [pulsar-io-21-8] INFO org.apache.pulsar.broker.service.ServerCnx - New connection from /10.6.1.187:57830
18:28:10.363 [pulsar-client-io-41-4] INFO org.apache.pulsar.client.impl.ConnectionPool - [[id: 0x43160072, L:/10.6.1.187:57830 - R:10.6.1.187/10.6.1.187:6650]] Connected to server
18:28:10.367 [pulsar-io-21-8] WARN org.apache.pulsar.broker.service.ServerCnx - [/10.6.1.187:57830] Unable to authenticate: Unsupported authentication mode: none
18:28:10.367 [pulsar-io-21-8] INFO org.apache.pulsar.broker.service.ServerCnx - Closed connection from /10.6.1.187:57830
18:28:10.367 [pulsar-client-io-41-4] WARN org.apache.pulsar.client.impl.ClientCnx - [10.6.1.187/10.6.1.187:6650] Got exception IllegalArgumentException : null
java.lang.IllegalArgumentException: null"
----
2019-06-21 21:42:21 UTC - el akroudi abdessamad: @el akroudi abdessamad has joined the channel
----
2019-06-22 00:36:51 UTC - Chris Bartholomew: @Sinan Bir have you configure token authentication in your websocket.conf file? Something like this:
----
2019-06-22 00:37:26 UTC - Chris Bartholomew: ```# Enable authentication
authenticationEnabled=true
# Autentication provider name list, which is comma separated list of class names
authenticationProviders=org.apache.pulsar.broker.authentication.AuthenticationProviderToken
# Enforce authorization
authorizationEnabled=true
# Authorization provider fully qualified class-name
authorizationProvider=org.apache.pulsar.broker.authorization.PulsarAuthorizationProvider
```
----
2019-06-22 03:09:19 UTC - Alexandre DUVAL: Yes. And when i Pulsar admin schémas get for this topic i got a 404
----
2019-06-22 03:09:41 UTC - Alexandre DUVAL: But the other one has no problem
----