I forgot to mention another option: Splunk can query webservices using the application rest_ta in the Splunk applications store. If you point that data source to
"https://netsight_ip:8443/axis/services/AppIdWebService/getLatestFlowsData?maxRows=number_of_flows&searchString=&source=purview_ip"
(I've been trying hard to avoid the Hub to interpret the previous as a real http link and formating it its own way, but no luck. If you need to see the full format of the url above, right click on the link above, select copy link and paste it somewhere  )
you get all flows in memory in purview with all their data. You will need to hack a bit with the coding of rest_ta application to process the data into Splunk but we can help you with that.
The problem with this approach is that every X seconds (the polling time in the rest_ta application) you get Y amount of flows (defined in the web service URL), irrespective if you already got them before which brings some challenges processing in Splunk duplicated flows, because you get them twice in successive webservices calls, or you may miss some flows because you didn't plan the number of flows to query and some of them have been aged before you issued the call.
Again, we are working finding solutions to these issues with specific Splunk configurations or redesigning the web service call to be published an update to the paper you already read