Yes, I am doing the same. And how to maintain the order of the dynamic properties in Invokehttp processor as the order is also important else it is saying bad request. Whenever i am adding those, these are automatically arranging the alphabetical orders instead the order on which i am adding  ... View more

@Fahmihamzah84 This appears to be an issue with your schema.  The BigQuery error is suggesting an issue trying to cast a string into a collection (array/list/ect).   It's hard to tell which array may be causing the issue as there are many.   My suggestion is to set the processor to log level DEBUG and see if you can get more verbose error.   This will help you figure out which field or fields is the culprit.      Keep in mind it could be one of the empty arrays too.     I do not suggest the following as a solution just as path to figuring out where the problem is.  Sometimes when i have issues with type casting,  i make everything a string temporarily and for development.  If you do this carefully one at a time, when the error goes away, you can determine which field it is.   This also helps you identify a working state for your flow and allow you to work from that operational base to find solution for the end schema being the format you need. ... View more

Awesome news, +2 solutions here.   ... View more

I increased the size of the ListenUDP processor and turned to false the content.repository.archive property and everything works again. Thanks for your reply  ... View more

Nice and Quick!  Excellent! ... View more

@fahed  That size is to be able to grow and serve in production manner.  At first that disk usage could be low.      For DataHubs,  My recommendation is to start small and grow as needed.   Most of your work load data should be in object store(s) for the data hubs,  so dont think of that "hdfs" disk as being size constrained to initial creations of the hub. ... View more

thank you steven!! I'll throw sqoop into the trash can. ... View more