[Bug] The default format of the manifest files is inconsistent.

[ChaomingZhangCN]

Search before asking

• I searched in the issues and found nothing similar.

Paimon-cpp version

The default format of the manifest files is inconsistent.

core_options.cpp

PAIMON_RETURN_NOT_OK(parser.ParseObject<FileFormatFactory>(
        Options::MANIFEST_FORMAT, /*default_identifier=*/"orc", &impl->manifest_file_format));
PAIMON_RETURN_NOT_OK(parser.ParseFileSystem(fs_scheme_to_identifier_map, specified_file_system,
                                            &impl->file_system));

CoreOptions.java

public static final ConfigOption<String> MANIFEST_FORMAT =
        key("manifest.format")
                .stringType()
                .defaultValue(CoreOptions.FILE_FORMAT_AVRO)
                .withDescription("Specify the message format of manifest files.");

Minimal reproduce step

When generating a plan for a table written in Java.

What doesn't meet your expectations?

Invalid: create orc file batch reader failed for file xxx, with Not an ORC file error

Anything else?

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!

[ChaomingZhangCN]

Changing the default value to avro directly can maintain compatibility with Java, but it will affect the reading of the inventory table. @lxy-9602, I'd like to hear your opinion.

[zjw1111]

Thank you for raising this issue!
We are currently adding support for the avro format(#31), and once implemented, we will soon adjust the default value of manifest to be consistent with Java.
As far as I know, very few production environment‘s users are currently using the C++ Paimon commit functionality, and furthermore, C++ Paimon has not yet publish a release version; thus, the impact caused by this compatibility issue is minimal.

[ChaomingZhangCN]

Thank you for your reply. It seems this issue will be fixed at #99, so I'll close this issue for now.

Thank you for raising this issue! We are currently adding support for the avro format(#31), and once implemented, we will soon adjust the default value of manifest to be consistent with Java. As far as I know, very few production environment‘s users are currently using the C++ Paimon commit functionality, and furthermore, C++ Paimon has not yet publish a release version; thus, the impact caused by this compatibility issue is minimal.