HI,
I have 3 PR's which are ready to merge from a couple of months.
Below are Kudu Processor PR's which got a couple of reviews by Kudu PMC
committer Grant Henke
Kudu Processor:
Kudu Put Operations, ready for merge
https://github.com/apache/nifi/pull/3610
Kudu Scan Operations, ready for merge
Thanks very much Erik, appreciate the feedback.
patw
On Thu, Aug 22, 2019 at 1:07 PM Erik Anderson wrote:
> IMO,
>
> Try and get the authentication working with a commandline utility like
> curl.
>
> When you get that working then try putting it into NIFI.
>
> At large corp's we generally use
IMO,
Try and get the authentication working with a commandline utility like curl.
When you get that working then try putting it into NIFI.
At large corp's we generally use SAML. We have talked about adding
SAML/Single-Signon to NiFi but, well, LDAP works just fine. NIFI+LDAP works
like a
Hi Folks,
Trying to get Nifi working with OpenID Connect authentication using Okta as
the OIDC provider. When Nifi has direct access to Okta, works fine. However
i have to run with a reverse proxy, that fails well into the OIDC token
fetch and redirect cycles with 401 'Unable to continue login
Hi all,
I have scenario where I need to read only the latest(the youngest) file
according to creation date. The files are:
Load_Dump_1.001.2019-07-22_17-22-45994.ifl - creation date
2019-07-22T17:24:44+0200
Load_Dump_1.001.2019-07-22_17-25-09132.ifl - creation date
2019-07-22T17:26:14+0200
So I
In that case, i guess the simplest way to improve things is to
understand where I got lost.
I successfully accessed the controller settings panel to add the nifi
registry.
But it was when I tried to add a process group that the permission issue
byte me.
So indeed, a tooltip (beside the
CaptureChangeMySQL -> ConvertJSONToSQL -> ExecuteSQL to replicate my database.
But when the field type is bit, there will be error. Because teh value is
parsed to '{}'
`is_cancel` bit(1) DEFAULT b'0' COMMENT 'canceled',
[ {
"id" : 6173148,
"task_id" : 6173148,
"charger_id" : 1,
Thanks very much, it works.
wangl...@geekplus.com.cn
From: Pierre Villard
Date: 2019-08-22 16:12
To: users
Subject: Re: ExecuteSQL ERROR if the field name is a sql keyword
Hi,
That's because your JSON contains a field with the name "value" which is a
reserved keyword. In the processor
Yeah me know we should try make things easier. On one side we want to have
a very fine-grained multi-tenant model for permissions and on the other
side we want user to quickly get up and running. If you have ideas to
improve the overall experience, any feedback is greatly appreciated.
I guess we
Well, ok, i've understood by clicking everywhere :-) (discoverability of
permission in nifi is ... ok ;-) ).
So, i've clicked the "manage access policies" item in the right-click
menu of the canvas and added my user everywhere, and now I can use the UI.
Thanks for your patience :-)
Le
By default the initial admin does not have permissions to do anything on
the canvas: the initial admin is usually used to manage users/groups and
apply policies to grant permissions to users/groups.
If you want to grant permissions to do something on the canvas, this is
done at process group
Well, I sort of sorted it out.
I can indeed login with my ldap, which is cool, but the whole UI is ...
grayed : I can't create process groups jor import existing ones.
So i took a look at the user screen.
My permissions are as follows
Global policy to access all policies write
Hi,
That's because your JSON contains a field with the name "value" which is a
reserved keyword. In the processor ConvertJSONToSQL, you can set the
property "Quote Column Identifiers" to "true". This will solve your problem
by using quotes around the column identifiers like suggested in the error
ConvertJSONToSQL -> ExecuteSQL
If the field name is the sql keyword, there will be error.
Is there any simple way to avoid this?
INSERT INTO t_stat_robot_poll (id, robot_id, shelf_code,
task_id, exe_task_id, task_type, exe_task_type, onload_flag, new_shelf_flag,
value, start_time,
14 matches
Mail list logo
