svenwesterlaken / mongo4j Goto Github PK

The devDependency semantic-release was updated from 15.13.16 to 15.13.17.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency mongoose was updated from 5.5.10 to 5.5.11.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mongoose is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency mongoose was updated from 5.2.17 to 5.2.18.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mongoose is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

How do I fix it? Thanks!

The devDependency jshint was updated from 2.10.0 to 2.10.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

jshint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I wrote neo_rel_name in my code, but there is not relationship shows up in neo4j.

DISCLAIMER: it is on my version of a save file.

Dear SvenWesterlaken

I have schema

const mongoose = require("mongoose");
const Schema = mongoose.Schema;
const mongoosastic = require("mongoosastic");
// const { schema } = require("./partNode");
const mongo4j = require("./plugins/mongo4j");
mongoose.set("debug", false);

// const NestedItemSchema = Schema({
//     id: { type: Schema.Types.ObjectId },
//     relScore: { type: Number, es_type: "long" },
// });

const PartanSchema = Schema(
    {
        desc: { type: String, es_indexed: true, neo_prop: true },
        metaDesc: { type: String, es_indexed: true },
        // mf: [
        //     {
        //         id: {
        //             type: Schema.Types.ObjectId,
        //             ref: "carModif",
        //             es_indexed: true,
        //             neo_rel_name: "MF_PT",
        //         },
        //         score: Number,
        //     },
        // ],
        
        gp: [
            {
                id: {
                    type: Schema.Types.ObjectId,
                    ref: "genPart",
                    es_indexed: true,
                    neo_rel_name: "GP_PT",
                },
                score: Number,
            },
        ],
    },
    { collection: "partan" }
);

PartanSchema.plugin(mongoosastic, {
    index: "partans",
    hosts: ["localhost:9200"],
    hydrate: true,
    hydrateOptions: { lean: true },
});
PartanSchema.plugin(mongo4j.plugin());

module.exports = mongoose.model("partan", PartanSchema);

// _id	name	partNumber	partSections	catalogs	analogsGroup

if I use only mf Array it works ok. It builds all the necessary nodes and relationships;
if I use only gp Array it works ok. It builds all the necessary nodes and relationships;

if I use both of them i get:

Neo4jError: Invalid input 'o': expected 'e/E' (line 3, column 257 (offset: 414))
"    ON MATCH SET doc.desc = 'тормозные колодки передние', doc.m_id = '5f9126b446cd8821bedf1a1b' WITH doc MATCH (I:Carmodif) WHERE I.m_id = '5f8e73cb62b1144467547ac7' MERGE (doc)-[r:MF_PT]->(I)  ON CREATE SET  r.score = 100 ON MATCH SET  r.score = 100WITH doc MATCH (II:Genpart) WHERE II.m_id = '5f8ebaa162b1144467547acf' MERGE (doc)-[r:GP_PT]->(II)  ON CREATE SET  r.score = 100 ON MATCH SET  r.score = 100"
                                                                                                                                                                                                                                                                 ^

    at captureStacktrace (/home/nikolay/code/nodejs/servers/elasticSearchSandbox/node_modules/neo4j-driver/lib/result.js:277:15)
    at new Result (/home/nikolay/code/nodejs/servers/elasticSearchSandbox/node_modules/neo4j-driver/lib/result.js:68:19)
    at Session._run (/home/nikolay/code/nodejs/servers/elasticSearchSandbox/node_modules/neo4j-driver/lib/session.js:174:14)
    at Session.run (/home/nikolay/code/nodejs/servers/elasticSearchSandbox/node_modules/neo4j-driver/lib/session.js:135:19)
    at Object.one (/home/nikolay/code/nodejs/servers/elasticSearchSandbox/node_modules/mongo4j/lib/save.js:30:13)
    at model.<anonymous> (/home/nikolay/code/nodejs/servers/elasticSearchSandbox/node_modules/mongo4j/lib/core.js:31:51)
    at callMiddlewareFunction (/home/nikolay/code/nodejs/servers/elasticSearchSandbox/node_modules/kareem/index.js:482:23)
    at next (/home/nikolay/code/nodejs/servers/elasticSearchSandbox/node_modules/kareem/index.js:193:9)
    at next (/home/nikolay/code/nodejs/servers/elasticSearchSandbox/node_modules/kareem/index.js:212:9)
    at Kareem.execPost (/home/nikolay/code/nodejs/servers/elasticSearchSandbox/node_modules/kareem/index.js:217:3)
    at _cb (/home/nikolay/code/nodejs/servers/elasticSearchSandbox/node_modules/kareem/index.js:307:15)
    at /home/nikolay/code/nodejs/servers/elasticSearchSandbox/node_modules/mongoose/lib/model.js:407:5
    at /home/nikolay/code/nodejs/servers/elasticSearchSandbox/node_modules/mongoose/lib/model.js:329:11
    at processTicksAndRejections (internal/process/task_queues.js:93:5) {
  code: 'Neo.ClientError.Statement.SyntaxError'
}

and it seems to me that problem could be in Cypher Query building

Neo4jError: Invalid input 'o': expected 'e/E' (line 3, column 257 (offset: 414))
"    ON MATCH SET doc.desc = 'тормозные колодки передние', doc.m_id = '5f9126b446cd8821bedf1a1b' WITH doc MATCH (I:Carmodif) WHERE I.m_id = '5f8e73cb62b1144467547ac7' MERGE (doc)-[r:MF_PT]->(I)  ON CREATE SET  r.score = 100 ON MATCH SET  r.score = 100WITH doc MATCH (II:Genpart) WHERE II.m_id = '5f8ebaa162b1144467547acf' MERGE (doc)-[r:GP_PT]->(II)  ON CREATE SET  r.score = 100 ON MATCH SET  r.score = 100"
                                                                                                                                                                                                                                                                 ^

As you can see it combines 2 queries in one.

Probably you will face the same issue when start to refactor code.

Dear, SvenWesterlaken!

I have faced a problem syncing 6k docs.

Everything works well on tens docs. But when I started syncing a little bigger amount of docs mongo4j stops my express server at all.
I have disconected mongo4j, added all the docs into mongo, reconnected mongo4j and faced timeout limitation.

(on video you can see how elastic search synced all the docs and mongo4j crashes after 60 seconds)
https://youtu.be/kefmJE2S6dQ

I have changed config, as shown below, but there was no effect

const mongo4j = require("mongo4j");
console.log("mongo4j is executiong....");
// mongo4j.init('neo4j://localhost', {user: 'neo4j', pass: '123'});
mongo4j.init(
    "bolt://localhost",
    { user: "neo4j", pass: "123" },
    {
        encrypted: "ENCRYPTION_OFF",
        maxConnectionLifetime: 3 * 60 * 60 * 1000, // 3 hours
        maxConnectionPoolSize: 150,
    }
);

const mongo4jDriver = mongo4j.getDriver();

console.log("mongo4jDriver", mongo4jDriver);

// create session
const s = mongo4jDriver.session();

// transaction
(async () =>{
    r = await s.writeTransaction(tx => f(tx), {
        timeout: 99999999 // define timeout
    });

})()

module.exports = mongo4j;

Do you have any idea how to overcome this obstacle?

PS. I have changed "neo4j://...." on "bolt://...." in driver config, because of this message
Neo4jError: Could not perform discovery. No routing servers available. Known routing table: RoutingTable[database=default database, expirationTime=0, currentTime=1605783019325, routers=[], readers=[], writers=[]]
as said in this article

The devDependency semantic-release was updated from 15.12.4 to 15.12.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency semantic-release was updated from 15.12.3 to 15.12.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

The dependency mongoose was updated from 5.4.13 to 5.4.14.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mongoose is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency semantic-release was updated from 15.9.15 to 15.9.16.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency travis-deploy-once was updated from 5.0.8 to 5.0.9.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

travis-deploy-once is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

What am I doing wrong?
I use mongoose and add mongo4j as a plugin.
There are 2 instances:
carMake:

const mongoose = require("mongoose");
const Schema = mongoose.Schema;
const mongoosastic = require("mongoosastic");
const mongo4j = require("./plugins/mongo4j");

mongoose.set("debug", false);

const CarMakeSchema = Schema(
    {
        name: {
            type: String,
            required: true,
            es_indexed: true,
            neo_prop: true,
        },
        syns: {
            type: Array,
            es_indexed: true,
            es_boost: 1.0,
            es_type: "string",
        },
    },
    { collection: "carMake" }
);

CarMakeSchema.plugin(mongoosastic, {
    index: "makes",
    hosts: ["localhost:9200"],
    hydrate: true,
    hydrateOptions: { lean: true },
});
CarMakeSchema.plugin(mongo4j.plugin());

module.exports = mongoose.model("carMake", CarMakeSchema);

// _id	name	partNumber	CarMakeSections	catalogs	analogsGroup

and carModel:

const mongoose = require("mongoose");
const Schema = mongoose.Schema;
const mongoosastic = require("mongoosastic");
const mongo4j = require("./plugins/mongo4j");
// const mongo4j = require("mongo4j");

mongoose.set("debug", false);
// mongo4j.init("neo4j://localhost", { user: "neo4j", pass: "123" });

const CarModelSchema = Schema(
    {
        name: {
            type: String,
            required: true,
            es_indexed: true,
            neo_prop: true,
        },
        syns: {
            type: Array,
            es_indexed: true,
            es_boost: 1.0,
            es_type: "string",
        },
        makes: {
            makeId: {
                type: Schema.Types.ObjectId,
                ref: "carMake",
                es_indexed: true,
                neo_rel_name: "MK_MD",
            },
            score: Number,
        },
        // makeId: {
        //     type: String,
        //     es_indexed: true,
        // },
    },
    { collection: "carModel" }
);

CarModelSchema.plugin(mongoosastic, {
    index: "models",
    hosts: ["localhost:9200"],
    hydrate: true,
    hydrateOptions: { lean: true },
});
CarModelSchema.plugin(mongo4j.plugin());

module.exports = mongoose.model("carModel", CarModelSchema);

// _id	name	partNumber	CarModelSections	catalogs	analogsGroup

And every time I save the project, my server restarts and I get new nodes and relationships to my Neo4j database.

"dependencies": {
        "axios": "^0.20.0",
        "axios-https-proxy-fix": "^0.17.1",
        "body-parser": "^1.19.0",
        "cheerio": "^1.0.0-rc.3",
        "cors": "^2.8.5",
        "csvtojson": "^2.0.10",
        "elasticsearch": "^16.7.1",
        "express": "^4.17.1",
        "fetch": "^1.1.0",
        "http-proxy-agent": "^4.0.1",
        "https-proxy-agent": "^5.0.0",
        "mongo4j": "^3.0.3",
        "mongoosastic": "^4.6.0",
        "mongoose": "^5.10.7",
        "node-fetch": "^2.6.1",
        "node-fetch-with-proxy": "^0.1.2",
        "nodemon": "^2.0.4",
        "puppeteer": "^5.3.1",
        "request": "^2.88.2",
        "request-promise-native": "^1.0.9",
        "selenium-webdriver": "^4.0.0-alpha.7",
        "socks-proxy-agent": "^5.0.0"
    }

What should I change to avoid creating nodes that are already in the database?

Or it is a feature with which I must live?)

video how it works

thanks)

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

The dependency neo4j-driver was updated from 1.7.4 to 1.7.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

neo4j-driver is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴