"<i1" and "<u1" unsupported by zarr driver about tensorstore HOT 2 CLOSED

Currently tensorstore expects those data types to be "|i1" and "|u1" since for a 1-byte type endianness does not matter.

It looks like zarr-python also seems to use "|i1" and "|u1" rather than "<i1" and "<u1". However, it would be reasonable for tensorstore to also support "<i1", ">i1", "<u1", ">u1" as equivalent, if it is helpful for interoperability.

Which zarr implementation is producing those dtypes?

from tensorstore.

NCZarr produced that file with <u1. And supporting (and ignoring) endianness for bytes is preferable, as it can be treated the same way as other integer types, e.g.:

std::string dtype;
if (SystemIsBigEndian())
{
  dtype = ">";
}
else
{
  dtype = "<";
}
if (std::numeric_limits<ElementType>::is_integer)
{
  if (std::numeric_limits<ElementType>::is_signed)
  {
    dtype += 'i';
  }
  else
  {
    dtype += 'u';
  }
}
else
{
  dtype += 'f';
}
dtype += std::to_string(sizeof(ElementType)); 

from tensorstore.