Hello everyone , When I am building any existing J...
# replication-troubleshooting
a
Hello everyone , When I am building any existing Java connector using the gradlew command , I am getting an error: Task : airbyte-integrationsbasesbase: airbyteDocker failed When I am following the stacktrace of the build , the error is happening due to IOexception: Create process error =193, %1 is not a valid Win32 application. It is unable to run build_image.sh program
t
Use WSL2 and run the gradle command from ubuntu terminal. It worked for me and that the recommended from airbyte. .Sh do not run on windows Follow this video for your setup.

https://www.youtube.com/watch?v=CtuU9Oi-6O8▾

a
I was trying to build the Java connector from git bash
I will try it with wsl
n
Let me know how it goes with WSL2!
a
I am following docs. Trying to do changes in the existing mongodb-v2 Java connector. I actually want to add a new text box where I take an input from UI and filter the data from mongodb on the basis of the input value. To achieve that thing, I first added that text box details in spec.json and tried to build the Java connector using gradlew command from documentation in git bash. It is failing in my case getting an error: Task : airbyte -integrations: basesbase airbyte Docker FAILED. I am not facing any issues in building any python connector.
n
Our team currently does not have the capacity to support custom connector development or additional development for existing connectors like this, unless you make a PR. I think more information is needed, but it looks like perhaps you need to double check that Java is correctly installed if this is affecting all Java connectors. I hope more people from the community chime in to help! 🙂
a
Thanks for replying, Nataly. Actually I was able to do changes in the existing python connector: YouTube analytics so I thought I could replicate the same process for a Java connector. I am gonna try it with wsl2. I even tried to build the Java connector in intellij but was getting the same error over there . I was following this airbyte discussion, FYI: https://discuss.airbyte.io/t/unable-to-create-dev-image-of-an-existing-destination-connector/303
It didn't work with wsl2 in my case. If anyone is aware of the steps to follow when changes have to be done in an existing Java connector for eg: mongodb-v2, please share here
t
WSL2 was to overcome the build.sh error as it was not able to execute the script. About making changes to the existing Java connector I am unaware of it. Have tried creating my own Java destination connectors using airbyte and it worked like a charm after WSL2
a
Actually that's what I am doing next, if editing the existing connector doesn't happen. I will build my own python source connector using airbyte -cdk for mongodb-v2 . But I was able to edit the existing python connector YouTube analytics so I thought I could do the same thing for Java connector like mongodb-v2
t
I guess it should allow to make changes in existing connector in an open-source.
a
Yes exactly. This is an open source tool. I am still exploring and kind of brute forcing through alternative solutions. I think the issue is with the compatibility of the gradle version and Java version. I also tried to build the Java connector in intellij and there also faced the same error.
@Andy Yeo (Airbyte) if you can share any kind of insights to the possible solution of the problem being discussed in this thread, that would be great
a
Hi @Aman Satya, it looks like this may be a windows-specific problem and in the past using WSL2 helped resolve issues but we’re not so familiar with Windows. @Nataly Merezhuk (Airbyte) is there anything else the team can help to debug here?
n
Hey @Aman Satya, please come to the community office hours: we have one every Wednesday at 11AM PST! In fact there is one today 🙂 I think this might be easier to debug while screen sharing https://airbyte.com/weekly-office-hours