2020-04-29 16:00:31 UTC - Sijie Guo: The error indicates that the user is authenticated but not auothorized. You need to make sure you grant super user permissions for function workers to run ---- 2020-04-29 16:12:53 UTC - Addison Higham: oh awesome! I got busy yesterday, was going to see if I could get a bit more data for it, sorry for not being more on top of it! If I learn anything else I will add comments there ---- 2020-04-29 16:45:56 UTC - Penghui Li: I have pushed a PR for fix this problem and I have test it on my laptop with geo-cluster. Please help review <https://github.com/apache/pulsar/pull/6846> ---- 2020-04-29 18:49:11 UTC - Addison Higham: super cool, mentioned in the topic, will try and hotfix out clusters ---- 2020-04-29 18:51:41 UTC - Addison Higham: is `namespaces set-schema-compatibility-strategy` correct to be superuser only? it seems like most superuser actions can effect the cluster, but that one seems to be pretty isolated to a namespace and would make sense to allow a tenant to decide on? ---- 2020-04-29 20:26:25 UTC - matt_innerspace.io: Are prometheus metrics still working? In my 2.5.1 instance, i see prometheus errors `expected equal, got "INVALID"` trying to consume the standard metrics at `pulsar:8080/metrics` . My config looks the same as it did for 2.4.1... ---- 2020-04-29 21:41:39 UTC - Sijie Guo: it should be working. did you curl the metrics to check the output first? ---- 2020-04-30 01:38:57 UTC - matt_innerspace.io: found the issue - one of my topic names contained a `"` (double quote), which was allowed by pulsar, but wasn't encoded in the metrics output, causing prometheus to throw an error parsing the output. ---- 2020-04-30 06:38:00 UTC - Sijie Guo: i see ----
