"URI scheme is not supported" for Neo4j Output about graphyx

[tlarsendataguy]

Ok, I was able to re-create the error on my end. There was a change in the way connections are managed between versions 3 and 4 of Neo4j. These tools were developed with version 4, which apparently does not play nice with version 3. Let me see if I can get backwards compatibility to version 3. Stay tuned.

[tlarsendataguy]

Hi @lalquier, thanks for submitting this issue.

Getting an error message like 'URI scheme not supported' would seem to indicate an issue with the url. Can you confirm whether you are including the scheme (http://) in the url textbox? For example, this is the configuration for an input tool on my laptop that points to a Neo4j Desktop instance:

The user is required to specify either http:// or https:// in the url.

FYI, the tool uses the http port to validate the query in the UI. The engine part of the tool also uses the http port to identify the bolt port. The engine will use the bolt protocol when sending queries to and receiving data from the Neo4j database. So even though you specify the HTTP address, bolt will actually be used for the data transfer.

Let me know if this resolves your issue, and if not, we can continue troubleshooting. In that case, it would be good to know which version of Neo4j and Alteryx you are using, as well as a screenshot of the tool configuration (with sensitive parts redacted) and errors in the workflow.

[lalquier]

Thanks for the reply.

I did use a fully formed URL to connect with HTTP.

I am using Alteryx 2021.2 and Neo4j 3.5.14

[tlarsendataguy]

Thank you for the additional information.

Specifically regarding the input tool, do you also get an error when you validate a query from the UI? Or does the error only happen when you run the workflow?

The 404 error is interesting because it indicates it cannot find the Neo4j server. Are you by any chance connecting through a proxy server?

[tlarsendataguy]

Just a quick update: I'm still trying to find the best way to support version 3 of Neo4j. The metadata provided by version 3's API is significantly messier than that in version 4. I've been struggling to find a way to reliably parse return values for the input tool. So I've not forgotten about this issue - it's just a harder problem than I first anticipated.