[Bug]: "test_graph_info_load_from_s3" failed under build type of Release about graphar HOT 8 CLOSED

seems it's arrow 12.0.0 bring the bug
https://github.com/apache/arrow/blob/fab79f50caf6a80eccaa3bbae79d518af7b408e5/cpp/src/arrow/filesystem/s3fs.cc#L2597-L2603

from graphar.

@acezen could you please help to have a look at this issue?

from graphar.

@acezen could you please help to have a look at this issue?

Ok, I'll take this and try to reproduce the bug.

from graphar.

En... It seems that arrow brings a AwsInstance class to manage the S3 filesystem in all arrow threads BUT did not take care of the life cycle of AwsInstance, they give the life cycle control to user, and user need to call FinalizedS3[2] when the S3 job is done.

[1]
[2] https://github.com/apache/arrow/blob/main/cpp/src/arrow/filesystem/s3fs.h#L340-L341

from graphar.

Consider to make a patch to GraphAr that add a FinalizedS3 static function to FileSystem and let user to finalize the S3 system manually. @lixueclaire what do you think?

from graphar.

Consider to make a patch to GraphAr that add a FinalizedS3 static function to FileSystem and let user to finalize the S3 system manually. @lixueclaire what do you think?

I agree that it would be helpful to add such a function to FileSystem in GraphAr to allow users to finalize the S3 system manually. And we could document this feature in the documentation to ensure that users are aware of this special processing requirement for the S3 system.

from graphar.

agree, thanks for the advise.

from graphar.

Open a keep track of upstream fix issue #187 ,close this one.

from graphar.