slfritchie has quit [Quit: Connection closed for inactivity]
CrashRoX has quit [Ping timeout: 260 seconds]
jonesnc has joined #wallaroo
pyroscope has quit [Ping timeout: 240 seconds]
pyroscope has joined #wallaroo
dipin has joined #wallaroo
dipin has quit [Client Quit]
jonesnc has quit [Quit: Leaving]
slfritchie has joined #wallaroo
dipin has joined #wallaroo
nicolai86 has joined #wallaroo
nicolai86 has quit [Remote host closed the connection]
vaninwagen has joined #wallaroo
dipin has quit [Quit: dipin]
dipin has joined #wallaroo
aturley has joined #wallaroo
vaninwagen has quit [Ping timeout: 240 seconds]
aturley has quit [Quit: aturley]
jonesnc has joined #wallaroo
<jonesnc>
are sinks meant to interact with databases like postgres or oracle? or am i misunderstanding sinks...?
<jonesnc>
or, put another way, does the wallaroo sink handle the interaction with the target External System, or is it only concerned with encoding the data so it's ready for processing with the External System
jonesnc has quit [Ping timeout: 240 seconds]
<SeanTAllen>
jonesnc: hopefully you see this later on. sinks are meant to interact with external systems. be an end point where data leaves wallaroo and goes somewhere else. That could be Kafka (or other thing in the message queue family) or over TCP, a file or a database. Currently we have TCP and Kafka sinks.
<SeanTAllen>
to directly answer your question. yes to "does the wallaroo sink handle the interaction with the target External System,"
jonesnc has joined #wallaroo
jonesnc has quit [Max SendQ exceeded]
jonesnc has joined #wallaroo
jonesnc has quit [Max SendQ exceeded]
jonesnc has joined #wallaroo
<jonesnc>
SeanTAllen: perfect! thanks for the response
<jonesnc>
i'm having connection issues today
<jonesnc>
i'm not sure if my messages are getting through
<slfritchie>
jonesnc: in this channel today, I've seen two: "are sinks meant...?" and "or, put another way, ..."
jonesnc has quit [Read error: Connection timed out]