[ 
https://issues.apache.org/jira/browse/ARROW-17372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marvin Giessing updated ARROW-17372:
------------------------------------
    Description: 
When trying to build the [feast go 
lib|https://github.com/feast-dev/feast/tree/master/go] on ppc64le it fails 
because parquet internal seems to miss even the basic (pure go implementations 
for ppc64le) files. Providing e.g. `bit_packing_ppc64le.go` & 
`unpack_bool_ppc64le.go` should solve this issue in the first place.

It can then be enhanced by implementing the correct vector & matrix intrinsics 
for the Power architecture (e.g. VSX or MMA) in a second step.


{code:java}
go build -mod=mod -buildmode=c-shared -tags cgo,ccalloc -o embedded_go.so .
cmd had error: exit status 2 output:
github.com/apache/arrow/go/v8/parquet/internal/utils
/root/go/pkg/mod/github.com/apache/arrow/go/v8@v8.0.0/parquet/internal/utils/bit_reader.go:230:18:
 undefined: unpack32
/root/go/pkg/mod/github.com/apache/arrow/go/v8@v8.0.0/parquet/internal/utils/bit_reader.go:274:3:
 undefined: BytesToBools
/root/go/pkg/mod/github.com/apache/arrow/go/v8@v8.0.0/parquet/internal/utils/bit_reader.go:318:18:
 undefined: unpack32 {code}
I tested this already locally (with success) and create an according PR.

  was:
When trying to build the [feast go 
lib|https://github.com/feast-dev/feast/tree/master/go] on ppc64le it fails 
because parquet internal seems to miss even the basic (pure go implementations 
for ppc64le) files. Providing e.g. `bit_packing_ppc64le.go` & 
`unpack_bool_ppc64le.go` should solve this issue in the first place.

It can then be enhanced by implementing the correct vector & matrix intrinsics 
for the Power architecture (e.g. VSX or MMA) in a second step.
go build -mod=mod -buildmode=c-shared -tags cgo,ccalloc -o embedded_go.so .
cmd had error: exit status 2 output:
{code:java}
github.com/apache/arrow/go/v8/parquet/internal/utils
/root/go/pkg/mod/github.com/apache/arrow/go/v8@v8.0.0/parquet/internal/utils/bit_reader.go:230:18:
 undefined: unpack32
/root/go/pkg/mod/github.com/apache/arrow/go/v8@v8.0.0/parquet/internal/utils/bit_reader.go:274:3:
 undefined: BytesToBools
/root/go/pkg/mod/github.com/apache/arrow/go/v8@v8.0.0/parquet/internal/utils/bit_reader.go:318:18:
 undefined: unpack32 {code}
I tested this already locally (with success) and create an according PR.


> Arrow parquet go is missing Power (ppc64le) specific utils implementations
> --------------------------------------------------------------------------
>
>                 Key: ARROW-17372
>                 URL: https://issues.apache.org/jira/browse/ARROW-17372
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Go, Parquet
>    Affects Versions: 8.0.0, 8.0.1
>         Environment: Linux (RHEL) ppc64le
>            Reporter: Marvin Giessing
>            Priority: Major
>
> When trying to build the [feast go 
> lib|https://github.com/feast-dev/feast/tree/master/go] on ppc64le it fails 
> because parquet internal seems to miss even the basic (pure go 
> implementations for ppc64le) files. Providing e.g. `bit_packing_ppc64le.go` & 
> `unpack_bool_ppc64le.go` should solve this issue in the first place.
> It can then be enhanced by implementing the correct vector & matrix 
> intrinsics for the Power architecture (e.g. VSX or MMA) in a second step.
> {code:java}
> go build -mod=mod -buildmode=c-shared -tags cgo,ccalloc -o embedded_go.so .
> cmd had error: exit status 2 output:
> github.com/apache/arrow/go/v8/parquet/internal/utils
> /root/go/pkg/mod/github.com/apache/arrow/go/v8@v8.0.0/parquet/internal/utils/bit_reader.go:230:18:
>  undefined: unpack32
> /root/go/pkg/mod/github.com/apache/arrow/go/v8@v8.0.0/parquet/internal/utils/bit_reader.go:274:3:
>  undefined: BytesToBools
> /root/go/pkg/mod/github.com/apache/arrow/go/v8@v8.0.0/parquet/internal/utils/bit_reader.go:318:18:
>  undefined: unpack32 {code}
> I tested this already locally (with success) and create an according PR.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to