I'm trying to connect Mongodb with Neo4j via APOC. I get a warning of deprecation:
This feature is deprecated and will be removed in future versions.
The query used a deprecated procedure. ('apoc.mongodb.get' is no longer supported)
EXPLAIN CALL apoc.mongodb.get('mongodb://localhost:27017','dataset','Product',{PieceId:1234}) yield value
The same happens with other procedures in apoc.mongodb. I haven't found any official communication that apoc.mongodb will be deprecated, so I'm thinking that I'm doing something wrong. Any idea?
Versions:
Neo4j 4.1.2
Neo4j Desktop 1.3.8
Plugins: apoc-4.1.0.1-all.jar,
apoc-mongodb-dependencies-4.1.0.1.jar
MongoDB 4.4.0 Community
Thanks,
Francesco
Related
Is there a postgres and keycloak version compatibility matrix? What is the latest postgres version compatible with Keycloak 20 ?
Unfortunately, there's no any matrix. In docs just a short and outdated list and some comments in Github discussions on why it's outdated.
Meanwhile, DB version for Java apps always depends on JDBC driver version.
So, the easiest way to find out what version of PostgreSQL is suitable for KC release is to take a look at versions of JDBC driver and PostgreSQL that specified in pom.xml. Switch to a release tag in the official repository, e.g. https://github.com/keycloak/keycloak/blob/20.0.3/pom.xml#L149-L150
The documentation here suggests Version 10.
The developer commits and issues only mention postgresql without versions. It doesn't matter which version you use, as long as it's supported!
See here for supported versions:
Supported versions
I'm running Solr 8.9.0 and Java 14.0.1 on Linux, and I'm trying to integrate Solr and MongoDB 5.0 Community Edition. I have MongoDB running and loaded with data, and I've installed the mongo-connector.
I'm really struggling with what to do next. All of the documentation that I've found (see a few examples below) is several years old, inconsistent, incomplete and simply doesn't work.
Can anyone please share some documentation / advice on how to integrate Solr and MongoDB?
Thank you.
Muhammad
https://blog.toadworld.com/2017/02/03/indexing-mongodb-data-in-apache-solr
https://hub.packtpub.com/apache-solr-and-big-data-integration-mongodb/
https://github.com/yougov/mongo-connector/wiki/Usage%20with%20Solr
https://chemifinder.wordpress.com/2015/08/19/integrating-mongodb-and-solr-part-3-integrating-mongodb-and-solr/
Hi I am trying to transport data from mongodb to elasticsearch. I have done it by following this tutorial. It is working for elasticsearch version 1.X. But when I tried to do it with version 5.X. plug-ins can't be installed. Can someone help me to figure out a way to do it with version 5.X.
These are the two plugins.
$ES_HOME/bin/plugin -install elasticsearch/elasticsearch-mapper-attachments/1.6.0
plugin --install com.github.richardwilly98.elasticsearch/elasticsearch-river-mongodb/2.0.9
In elastic 5.x+ the installation commands are different. The mapper attachment library you're trying to install has an example here
bin/plugin install elasticsearch/elasticsearch-mapper-attachments/3.1.2
The other library does not mention support of Elastic > 2.x, and its last commit was well before 5.x existed.
If you need to use that exact library, I don't believe you will be able to use anything > 2.x
We have an app that uses the C# Mongodb client lib from mongo, version 1.1.0.4184
This code currently runs against mongodb 2.6.4
We would like to stand up a new mongodb server, the current version (3.2.11). Will our code run against newer mongodb?
It really depends what you mean by "will it run". The MongoDB v1.1.0.4184 C# driver was released in June, 2011 and dates to roughly the MongoDB 1.8 server release timeframe. This driver version is certainly no longer tested or supported, and will not be fully compatible with newer server features like the WiredTiger storage engine (default in MongoDB 3.2+) or SCRAM-SHA-1 authentication (default in MongoDB 3.0+).
The MongoDB documentation includes a reference table with recommended version(s) of the drivers for use with a specific version of MongoDB: C#/.NET Driver Compatibility.
If this is a production system I would strongly recommend taking the time to update and test a supported version of the C# driver for use with MongoDB 3.2 (eg. the v1.11 C# driver). I suspect it is very likely you will encounter fixed (or novel) bugs/behaviour using a driver that is more than five years old. Your application won't be able to take advantage of many of the newer server features, and this obsolete driver predates specifications such as standard Server Discovery and Monitoring (SDAM) behaviour.
That said, assuming you aren't using any features the driver isn't aware of your code may continue to run (or at least appear to run) successfully. In my opinion doing so is a high risk deployment strategy.
Yes, i am using it, but however we have to chek on specific features, which you were using. using MongoDB latest driver is much better in terms of latest features and there are few features were removed(like 'eval()').
As a newbie, I followed this link:
http://www.blakeerickson.com/posts/2013/04/07/how_to_correctly_configure_ubuntu_to_run_lithium_php
and this link:
http://li3.me/docs/manual/quickstart
to install and run the Lithium tutorial. Everything is OK until the MongoDB accessing. I got the following:
Deprecated: Mongo::__construct(): The 'timeout' option is deprecated. Please use 'connectTimeoutMS' instead in /home/takpo/www/my_app/libraries/lithium/data/source/MongoDb.php on line 261
Quickstart
Manual
API
More
⟁
© Union Of RAD 2013
message and the form items are not seen. Could someone help?
Thanks,
Tak
You should upgrade to Lithium's latest master.
It's caused by PHP mongo extension. if you use < 1.3.4 you won't see the problem, but Lithium latest master fixed it.