There is a branch that builds ZetaSQL on Mac, it only works with Bazel
0.25.3. You would need XCode to build it locally. After you build it, and
put jnilib into classpath, it just works. One of my colleagues has updated
this branch to the latest release [1].

/Gleb

[1]: https://github.com/csenel/zetasql/tree/darwin-build

On Mon, Mar 16, 2020 at 8:26 PM Tomo Suzuki <[email protected]> wrote:

> I see. Thank you. I also found Alex's ticket for zetasql.
> https://github.com/google/zetasql/issues/25
>
> Closing thread.
>
> Regards,
> Tomo
>
> On Mon, Mar 16, 2020 at 3:21 PM Andrew Pilloud <[email protected]>
> wrote:
>
>> That error is expected unless you've built your own jar with
>> liblocal_service_jni.jnilib for OS X. A few have tried but no one has
>> succeeded (as far as I know), it is on the ZetaSQL team's todo list. You'll
>> need to run that module on Linux for now.
>>
>> See: https://github.com/google/zetasql/pull/3
>>
>> Andrew
>>
>> On Mon, Mar 16, 2020 at 12:09 PM Tomo Suzuki <[email protected]> wrote:
>>
>>> Hi Beam developers,
>>>
>>> I started getting test failures when building Beam in my MacBook Pro.
>>> Module: sdks/java/extensions/sql/zetasql. The NoClassDefFoundError occurs
>>> because of jnilib file is missing.
>>>
>>> Caused by: java.lang.RuntimeException: java.io.FileNotFoundException:
>>> File /zetasql/local_service/liblocal_service_jni.jnilib was not found
>>> inside JAR.
>>> at
>>> com.google.zetasql.JniChannelProvider.<clinit>(JniChannelProvider.java:68)
>>> ... 69 more
>>> Caused by: java.io.FileNotFoundException: File
>>> /zetasql/local_service/liblocal_service_jni.jnilib was not found inside JAR.
>>> at
>>> com.google.zetasql.cz.adamh.utils.NativeUtils.loadLibraryFromJar(NativeUtils.java:105)
>>> at
>>> com.google.zetasql.JniChannelProvider.<clinit>(JniChannelProvider.java:66)
>>> ... 69 more
>>>
>>> Full log:
>>> https://gist.github.com/suztomo/f3d8815e8f48aeabd0288de34c1488f0
>>>
>>> Has anyone encountered a similar problem?
>>>
>>> --
>>> Regards,
>>> Tomo
>>>
>>
>
> --
> Regards,
> Tomo
>

Reply via email to