i have experienced this bug when using Pig jobs writing their output to a Swift container. running the example Pig job from extras with a DataSource output to a container will create an "output" pseudo directory with the true output files in it, and it creates a file named "output" that is zero byte.
i have experienced this bug when using Pig jobs writing their output to a Swift container. running the example Pig job from extras with a DataSource output to a container will create an "output" pseudo directory with the true output files in it, and it creates a file named "output" that is zero byte.