We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I noticed in the client code you have the following:
var putProcessGroupFlow = function(uuid, pg, callback) { this.putComponent('/flow/process-groups/' + uuid, pg, callback); }
When we execute the following:
nifiApi.updateProcessGroupState(groupId, true, (err, result) => { if (err) return console.log('Failed to start a processor', err); console.log(result); });
It throws an error because the URL ends up being:
http://10.29.61.93:8080/flow/process-groups/6f774aa3-015f-1000-4cae-a6b5d7df5f07
Instead of:
http://10.29.61.93:8080/nifi-api/flow/process-groups/6f774aa3-015f-1000-4cae-a6b5d7df5f07
Should your code be changed to (removing / from the beginning):
this.putComponent('flow/process-groups/' + uuid, pg, callback);
or are we missing something?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I noticed in the client code you have the following:
var putProcessGroupFlow = function(uuid, pg, callback) { this.putComponent('/flow/process-groups/' + uuid, pg, callback); }
When we execute the following:
nifiApi.updateProcessGroupState(groupId, true, (err, result) => { if (err) return console.log('Failed to start a processor', err); console.log(result); });
It throws an error because the URL ends up being:
http://10.29.61.93:8080/flow/process-groups/6f774aa3-015f-1000-4cae-a6b5d7df5f07
Instead of:
http://10.29.61.93:8080/nifi-api/flow/process-groups/6f774aa3-015f-1000-4cae-a6b5d7df5f07
Should your code be changed to (removing / from the beginning):
this.putComponent('flow/process-groups/' + uuid, pg, callback);
or are we missing something?
The text was updated successfully, but these errors were encountered: