Rishi321

Ok, I see that every request may end up with a new schema based on the includes and other attributes, but when calling these from an API client there will...

This must have something to do with an integer overflow as two attempts stopped at the exact same byte size 36339319354 Feb 12 13:48 xxx_2019-02-12T11-38-35.gz 36339319354 Feb 13 08:15 xxx_2019-02-13T06-08-39.gz...

As a sidenote: The documentation is using commas as delimiters for the convert, whereas only newlines work. It gives a configuration error otherwise