Hi @JoeCap08055, thanks for correcting the MIME type.

I failed to find any trace of documentation mentioning PARE is used as a magic byte signature for Apache Parquet files.
Can you clarify where this comes from and why we should include that signature?
Do you have an original file using that signature you can share?

Hi @JoeCap08055, thanks for correcting the MIME type.

I failed to find any trace of documentation mentioning PARE is used as a magic byte signature for Apache Parquet files. Can you clarify where this comes from and why we should include that signature? Do you have an original file using that signature you can share?

@Borewit I saw it in the official IANA descriptor here

Additional information:

1. Deprecated alias names for this type: x-parquet
2. Magic number(s): PAR1, PARE
3. File extension(s): .parquet
4. Macintosh file type code: not available
5. Object Identifiers: not available

Also, see this GH issue that calls out "PARE" as being a magic number for Parquet files with encryption:
apache/parquet-format#381

Side note: the Parquet docs only specifically refer to "PARE" being used for an encrypted file footer, not the header, so technically it wouldn't apply to file type determination, but it also can't hurt--and as it's a registered IANA magic number, it can't be misinterpreted as some other type.

@Borewit Your call on whether to leave the check in the code for "PARE" or not.

Thanks for providing the background @JoeCap08055 , makes total sense to include that one indeed.

Looks good to me, but this is a breaking change and must wait for the next major version.

Looks good to me, but this is a breaking change and must wait for the next major version.

@sindresorhus that's unfortunate, but makes sense--is there a rough estimate of when that's expected?

@sindresorhus , we now have a number PR's with some minor API changes, I think this is a good moment to start merging those and start to work towards a major release.