When should you disable JMS for source collections?

#1

When should you disable JMS for source collections (SourceCollection.jmsDisabled)?

What exactly does this do?

This is what the documentation says:

if set to true then it will call Source#imprt in sync or processInbox by default it will load data for the SourceCollection using JMS for backwards compatibility

But what are the impacts of using Source#imprt in sync or processInbox versus loading the data using JMS?

0 Likes

#2

@garrynigel can you please elaborate

1 Like

#3

@Slooz @yaroslav This flag was introduced temporarily to avoid chunking used by the dataloading pipeline. In the past we have had experiences that chunking using JMS was kind of unreliable, either JMS would give up or we would have remote connectivity issue.

In 7.8.1 this flag will be removed and introduce doNotChunk flag. And chunking would be managed by C3 internally (development is going on as we speak :slight_smile: )

use jmsDisabled set to true.

  1. if you have small sample files you want to load into C3
  2. if you have large amount of files and you want to load all of them in parallel without roundtripping to JMS

use jmsDisabled set to false
If you want to leverage chunking, for files which are very large, and you want to load them quickly.

2 Likes

#4

Thank you @garrynigel!

0 Likes