---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/31881/
---
Review request for samza.
Bugs: SAMZA-506
https://issues.apache.org/jira/br
Thanks for the response Chris. I opened
https://issues.apache.org/jira/browse/SAMZA-589. A prefix seems like the
easiest thing. Would be nice if the keys still show but the values appear
masked.
From: Chris Riccomini [criccom...@apache.org]
Sent: Mond
Hey Tommy,
Yea, this has come up a few times. We don't currently have an answer for
it. The simplest thing to do would be to have a prefix. Any config with the
prefix could be stripped from the AM and logs. Another possibility is to
store the configs in an encrypted way, and have the code decrypt
We have some sensitive information that we are currently storing in the Samza
config. Our ops guys have some concern regarding where the config is displayed
(e.g. in logs, app master UI, etc). I'm curious if others have had similar
concerns and if so what you did about it. Seems like we migh
Hi, Julian,
Thanks for the reply. I want to make sure that I understand your
explanation on windows in JOIN more explicitly.
For the following case:
Q.1) SELECT STREAM id, cost, value, Shipments.rowtime as shiptime FROM
Orders OVER (ORDER BY rowtime RANGE '3' min PROCEDING)
JOIN Shipments OVER
