Vishwanatha-HD commented on PR #48200:
URL: https://github.com/apache/arrow/pull/48200#issuecomment-3570795846

   > @Vishwanatha-HD
   > 
   > Looking over this batch of tests, a few patterns in how the expected bytes 
are formed caught my eye. Nothing alarming — just places where BE ends up 
taking a slightly different journey than LE depending on where the 
normalization happens.
   > 
   > • Half-floats: the assertions use the raw bits from the array, so BE 
naturally ends up comparing against host-order patterns unless those values get 
flipped before they reach the check.
   > 
   > • INT96 and other scalar stats: some expected strings are built straight 
from native-order limbs, which means the two architectures diverge a bit unless 
they’re pushed through one consistent conversion point.
   > 
   > • ByteStreamSplit: since the inputs to the encoder come in as native-order 
integers, the resulting split streams follow whatever the host layout is unless 
they’re normalized up front.
   > 
   > • Page-index and stats checks: a few comparisons still assume host-order 
for floats/doubles, while others already expect swapped limbs.
   > 
   > Individually these are all reasonable, but they do lead to small 
differences on BE because the tests anchor themselves at slightly different 
spots in the pipeline. Pulling the expectations toward one shared byte layout 
in a couple of places would likely smooth that out across hosts.
   
   @k8ika0s.. Thanks for your review comments.. But please note that we are 
already taking care of the conversion required in encoders and decoders.. Hence 
we need to take care of the corresponding testcases accordingly.. 
   I have tested with my changes on the s390x systems and also on Openshift AI 
workloads.. It works properly.. Hence there is no concern with these changes.. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to