rohanjain101 opened a new issue, #35957:
URL: https://github.com/apache/arrow/issues/35957

   ### Describe the bug, including details regarding any error messages, 
version, and platform.
   
   ```
   >>> arr1 = pa.array([decimal.Decimal("1.23")])
   >>> arr2 = pa.array(["abc"])
   >>> pa.compute.greater(arr1, arr2)
   Traceback (most recent call last):
     File "<stdin>", line 1, in <module>
     File "C:\ca2_ps_311\Lib\site-packages\pyarrow\compute.py", line 242, in 
wrapper
       return func.call(args, None, memory_pool)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
     File "pyarrow\_compute.pyx", line 367, in pyarrow._compute.Function.call
     File "pyarrow\error.pxi", line 144, in 
pyarrow.lib.pyarrow_internal_check_status
     File "pyarrow\error.pxi", line 100, in pyarrow.lib.check_status
   pyarrow.lib.ArrowInvalid: Not an integer type: 13
   >>>
   ```
   
   I would expect this to raise a kernel matching error, it seems thats the 
error that would be raised for all cases other than decimal:
   
   ```
   >>> arr2 = pa.array(["abc"])
   >>> arr3 = pa.array([1.23])
   >>> pa.compute.greater(arr2, arr3)
   Traceback (most recent call last):
     File "<stdin>", line 1, in <module>
     File "C:\ca2_ps_311\Lib\site-packages\pyarrow\compute.py", line 242, in 
wrapper
       return func.call(args, None, memory_pool)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
     File "pyarrow\_compute.pyx", line 367, in pyarrow._compute.Function.call
     File "pyarrow\error.pxi", line 144, in 
pyarrow.lib.pyarrow_internal_check_status
     File "pyarrow\error.pxi", line 121, in pyarrow.lib.check_status
   pyarrow.lib.ArrowNotImplementedError: Function 'greater' has no kernel 
matching input types (string, double)
   >>>
   ```
   
   ```
   >>> pa.__version__
   '12.0.0'
   >>>
   ```
   
   
   
   ### Component(s)
   
   Python


-- 
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