Join the free virtual developer conference on knowledge graphs and AI. This year's themes are: applications, AI engineering, data intelligence, graphs, and architecture.
I just finished the first level and set the parameter to 2. So I tried to include the next level with exactly the same code as before and got the following error:
if one tries to connect to said URL using a browser the response is
{"error":{"code":"invalidtitle","info":"Bad title \"Category::Ma\u00dftheorie\".","*":"See https://de.wikipedia.org/w/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."},"servedby":"mw1410"}
I tried it completely again and it works fine with the English wikipedia and just one :. With the german Wikipedia I have to run it twice. First with :: and after that I have to run it again with just one :, because i get more subclasses. (don't know why)
But now I have a Neo.ClientError.Transaction.TransactionTimedOut. Error.
Neo.ClientError.Transaction.TransactionTimedOut
The transaction has been terminated. Retry your operation in a new transaction, and you should see a successful result. The transaction has not completed within the specified timeout (dbms.transaction.timeout). You may want to retry with a longer timeout.
My solution idea is to set the timeout longer. I found the following code at the Transaction Management. dbms.transaction.timeout=10s.
Is this the correct command? Cause I have trouble using it in the sandbox.
The Neo.ClientError.Statement.SyntaxError says this is an invalid input and it is expecting an operator in combination with the command like "SET". So I tried to put it in front of the command, but then it respond another syntax error.
did encoding the url help per my last update?
and im really confused as to why running the same command 2x results in he first time failing and the 2nd, and the same command, then succeeding
As to dbms.transaction.timeout as you experienced this is not configured via a SET command. Though I'm also not aware of SET being valid at all. dbms.stransaction.timeout is typically defined in the conf/neo4j.conf file or you can dynamically set using call dbms.setConfigValue(); see https://neo4j.com/docs/operations-manual/4.2/configuration/dynamic-settings/ though this documentation speaks of Neo4j v4.2 . It should be valid for all 4.x versions but as there is no prior detail of what version of Neo4j is in play here if you are pre 4.x then call dbms.setConfigValue(); may not be valid