TY-Connector | Connector for Tuya Devices with SmartThings | Runtime Evironment library

If you want to be able to connect to any node in the cluster and consume messages sent to any other node in the cluster then you need to set your redistribution-delay to something >= 0. The default redistribution-delay is -1 which means messages will never be redistributed. The documentation is pretty clear about this. Here's an example configuration:

There are a few additional changes that you need to make to the original function from the tutorial:

• Probably you won't use the requestedFields parameter as it is used in the tutorial, since it's an object based on what is used by Data Studio. So you can remove it and just go over the keys of each object you're passing (see code below).
• The parsedResponse argument is not used in the function and you're using response instead, so you need to change the argument's name as well.
• The function inside map is missing an argument name that will be used when pushing values to the row inside the switch (see code below). I named it transaction, but you can use another name if you want.

Doing these modifications, the code becomes something like the following:

As of 11/3/2020, this problem of not being able to use PATH_USER_PASS has been resolved. I didn't change any code but that option of authentication works now.

Using 0.0.0.0 for a connector is not valid. In fact, there should be a WARN level message in the log about it. Your cluster will not form properly with such a configuration. You need to use a hostname or IP address that other hosts can use to reach the broker that broadcasts it. That's the whole point of the broadcast-group - to tell other brokers who may be listening how they can connect to it.

Network bridge is the default network driver used by docker and creates a virtual interface in the container that’s not available on the host but allows containers connected to the same bridge network to communicate.

The IP address of the broker used in broker.xml for the connector and the acceptor should match with the IP address of the container virtual network interface. This IP address is assigned dynamically but docker-compose allows to define a custom network with a fixed addresses, ie:

What you're seeing is expected.

In an ActiveMQ Artemis HA pair (i.e. a master & slave) one broker will be active and one broker will be passive. If you look at the management console of the active broker you'll see all the normal runtime data (e.g. addresses, queues, message counts, connection counts, etc.). However, if you look at the management console of the passive broker you'll see very little because the broker is passive. It has not loaded any of the message data (since it's not active). It doesn't have any client connections, etc.

Based on all the information you've provided so far everything seems to be working fine. The documentation you cited says:

These cluster connections allow messages to flow between the nodes of the cluster to balance load.

And when you send a STOMP message to one node you are able to consume it from the other which means that messages are flowing over the cluster connection between nodes on demand to balance load.

You don't need any additional cluster connections or connectors.

To be clear, each broker in the cluster will have its own set of addresses, queues, and messages depending on what the clients connected to them are doing. You shouldn't necessarily expect to see all the same addresses or queues on all the different nodes of the cluster - especially if you are relying on automatic creation of addresses and queues rather than pre-configuring them in broker.xml.

That said, you will see some different behaviors from applications using the JMS client (e.g. your Spring app) and applications using STOMP. This is because the STOMP protocol doesn't define anything related to advanced concepts like connection load balancing, failover, etc. STOMP is a very simple protocol and clients are usually quite simple as well. Furthermore, Spring applications typically create multiple connections. Those connections be balanced across the nodes in the cluster in a round-robin fashion which is almost certainly why those related addresses and queues appear on all the nodes and the ones for your single STOMP client do not. Client-side connection load-balancing is discussed further in the documentation.

Messages are distributed by the nodes themselves independent of the protocol used. That's the whole purpose of the cluster connections - to forward messages to other nodes.

Client connections can't be automatically distributed by the nodes themselves because that would require redirects and not all protocols (e.g. STOMP) support those semantics.

1) File Upload (Official CSV Connector by Google)

• How about using the CSV Connector by Google?
• Added a GIF showing the location from the Google Data Studio page:

2) Google Sheets (Alternative solution):

• There are two ways to import CSV data to Google Sheets:
  1. Import Data Set: Opening and saving the CSV file as a Google Sheet
  2. IMPORTDATA: The function imports CSV data from a URL
• Added an Editable Google Sheet along with a GIF to demonstrate the IMPORTDATA function:

3) Fetch CSV Community Connector:

• The Fetch CSV Community Connector is not an Official Google connector, however it's an open source connector, so perhaps a user could have a look through provide some insights (it would be better to update the question with the relevant code). In addition, you could reach out to the authors of the connector by creating a New Issue.

The date field is currently detected and formatted as a Text field. To ensure that the date field is a Google Data Studio recognised Date field, create the following Calculated Field that uses the TODATE function:

The error stating "Unblocking a blocking call that will never get a response" is expected if failover happens when the client is in the middle of a blocking call (e.g. sending a durable message and waiting for an ack from the broker, committing a transaction, etc.). This is discussed further in the documentation.

The fact that clients don't switch back to the master broker when it comes back is also expected given your configuration. In short, you haven't configured failback properly. Your master should have: