@LKB  I recommend creating a new community question with the details around yoru setup and exceptions you may be seeing.  You are more likely to get better traction on a community question that does not already have and accepted solution. Thank you, Matt ... View more

though i gave the permission to view user interface, i am still facing this issue. ... View more

@LKB  Can you share screenshots of your UpdateAttribute processor configuration? Are you using the advanced UI of the UpdateAttribute processor? The UpdateAttribute processor is fairly simplistic in design. Without configuring the advanced UI, it simply can remove attributes or create/modify existing attributes.  Each Attribute is defined by key:value pairs where the property name is the key and property value is the key.  The Advanced UI allows for conditionally based attribute additions or modifications. If you found any of the suggestions/solutions provided helped you with your issue, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt   ... View more

@mburgess  I am trying to run a merge query in PUTSQL after using ExecuteSQL to pull from source database. I then pass the results through ConvertAvrotoJSON and then to convertJSONToSQL (set to INSERT since there is no UPSERT for SQL server database). I want to now run the merge query to update if the primary key is matched or insert if not, but I have been getting all sorts of errors Input flowfile has the following attributes sql.args.1.type 12 sql.args.1.value A-001 sql.args.2.type 12 sql.args.2.value DDD sql.args.3.type 12 sql.args.3.value 2B sql.args.4.type 12 sql.args.4.value AAA sql.args.5.type 12 sql.args.5.value 2B sql.args.6.type 12 sql.args.6.value BBB sql.args.7.type 93 sql.args.7.value 1954-08-01 22:46:50.73 sql.catalog CUSDB sql.table CUSTOMERS uuid 50a3daf9-e5d8-422b-b6cb-9c92da723c55 I created the following attributes in UpdateAtributes I directed this flowfile to UpdateAttribute where I created above properties like this   sql.args.1.type = 12;  sql.args.1.value = ${vkey} sql.args.2.type = 12;  sql.args.2.value = ${AP} sql.args.3.type = 12;  sql.args.3.value = ${BP} ........ sql.args.7.type = 93;  sql.args.7.value = ${LAST_MOD_DATE} But when I check the results of the queue of the UpdateAtributes, I see that sql.args.1.type, sql.args.2.type, ... sql.args.7.type return blank values. I am doing something wrong in the way I have defined those properties? Merge query in PutSQL looks like this MERGE INTO RCDB.dbo.RCDB_WELLHEADER_HZ_NIFI_V2 as t USING (select ? as vkey, ? as ap, ? as bp, ? as lm, ? as lnum, ? as wn, ? as LAST_MOD_DATE) s ON t.EKEY = s.EKEY WHEN MATCHED THEN UPDATE SET t.ap = s.ap, t.bp = s.bp, t.lm = s.lm, t.lnum = s.lnum, t.wn = s.wn, t.LAST_MOD_DATE = s.LAST_MOD_DATE WHEN NOT MATCHED THEN INSERT (vkey, ap, bp, lm, lnum, wn, LAST_MOD_DATE) VALUES (?, ?, ?, ?, ?, ?, to_date(?, 'YYYY-MM-DD HH34:MI:SS')) I get the error that all parameters are blank. Can someone please point me in the direction to resolve this issue. Why are the attributes going blank when I set them in UpdateAttributes?   ... View more

@LKBand if you try the below select, what error do you encounter? Unfortunately I have no MS SQL database with which I could test so I can only somehow help you debug your situation, one step at a time.   select "06 QQQ" as 66_QQQ, "11 JJJ" as 11_JJJ, "12 KKK" as 12_KKK, "13 JJJ" as 13_JJJ from DB_TEST.dbo.FGRID -- or with ` instead of " -- or QQQ_66, sending the number at the back of the column, instead of the front.   I assume that you have your Record Writer configured as Inherit Record Schema. ... View more

@LKB  I'd expect a full stack trace in the nifi-app.log following that ERROR. The ldap-provider is configured inside the login-identity-providers.xml file.  Does your LDAP Manager password happen to contain any XML special characters?  If so, you should escape them. https://xml.silmaril.ie/specials.html Have you tried using ldapsearch to manually make a connection to your LDAPS from the server where you have NiFi installed using same manager DN, Manager password, and keystore and trustsore?  Was it successful? If you found any of the suggestions/solutions provided helped you with your issue, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt ... View more

@raobelina_toky_  Looking at the resolution of your NiFi issues on LDAPS, I have the following questions around Keystore/truststore 1. I am currently using the same keystore/truststore that was internally generated by our identity management team when I had configured for singleuser mode for my LDAP configuration. Does a new one need to be generated for my initial admin user to be able to connect to NiFi? Right now I can't connect with initial admin user. My knowledge of the way keystore/truststore work is very scanty. 2. Can you share the present settings of your authorizers.xml, login-identity-provider.xml that is working (without passwords, of course). I am able to start NiFi with my settings but just can't connect with initial admin user. I have a feeling that it's keystore/truststore issue but can't seem to resolve it   ... View more

@LKB  You would get better traction/feedback if you start your own community question.  Your query is not very related to issue in this post.    As far as the one question related to this post about encrypted manager password,  @mks27 simply masked it by using "***" in his post.  NiFi does not replace actual password with * when encrypting sensitive passwords. The NiFi Encrypt-Config Toolkit  can be used to encrypt passwords used in various NiFi configuration files: https://nifi.apache.org/docs/nifi-docs/html/toolkit-guide.html#encrypt_config_tool Thank you, Matt ... View more