Pinging directly will not work as it is behind the firewall.  We need to use curl pointing to the proxy to connect to cloudera.com at the OS level (could be any internet hostname) My previous responses tested using curl calling our proxy server at the OS level where NiFi is running and it is working. Only NiFi using Configuration service (Proxy server: HTTP) seems to broken with 2.7.2.  Before the upgrade from 1.26 to 2.7.2, NiFi worked connecting to cloudera using our own proxy server. ... View more

@zhouweibo  As mentioned previously, please provide the DDL, sample data, and corresponding SQL to reproduce the problem. With this information, we can reproduce the problem locally and  offer an exact working solution.  ... View more

Hi @haridjh I tried to delete the VC using `cdp de delete-vc --vc-id...  --cluster-id...` and got an error result of auth failed: (Status Code: 403; Error Code: PERMISSION_DENIED; Service: de; Operation: deleteVc; Request ID: 94ac6721-5242-43d2-963b-c5b907ca030c;)   ... View more

@Pashazadeh  Apache NiFI 2.0.x was a technical milestone/preview releases that underwent many changes before the first GA release with NiFi 2.1.x.  I would not expect a change in behavior going forward, unless some bug is introduced or the community agrees on a change in functionality/behavior.   While I don't have a specific answer to what bug resulted in the difference in behavior you encountered, here are some changes that affected the JsonRecordSetWriter. NIFI-14331 NIFI-13963 / NIFI-13843 NIFI-12670 If you still have your NiFi 2.0.0 running, you could run your flow using a convertRecord with same record readers and writers and then compare the output content with what you see with 2.7.1 output.  Maybe that can help figure out what is happening and if either of those bugs affecting earlier NiFi 2.x versions is related. Thanks, Matt ... View more

Hello @shubham_rai  Could you please provide an update on this? Was the hive on Tez not restarted, or was a false stale entry present on the hive on Tez? Was a restart required or stale entry icon was gone on its own? Did you find any error in CM server logs? Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. ... View more

Thanks Matt, thats a very useful explanation. ... View more

Thanks for responding with a resolution that worked for you, @Pedro_E. I'll mark your response as a solution.  ... View more

@hshaikh, Did the response assist in resolving your query? If it did, kindly mark the relevant reply as the solution to help others find the answer more easily in the future. ... View more

Hello Andrés, Yes we had a look at it, in fact it seems it's really solved with 2.7 with https://issues.apache.org/jira/browse/NIFI-14959. I add a look at the code fix provided and well it seems to concern really this partition by attribute. By the way, when we saw this defect, I tried another test. I create a dummy attributs and assign randomly a value 0 - 10 and then tried the partition load by this atrribute. This was even worst than the load balance strategy(I had less reccords processed than the third I had with load balace strategy). If it was the same kind of issue, I was expecting to have roughly the same amount of processed reccords. I say roughly because in this second test I had perhaps 10% of the reccords processed vs 33% with the load balance strategy. In addition, we are not big fans of pushing to our Prod right now a version (2.7.1) which has been released 3 days ago only.  That was why we were searching if someone else faced the issue or if someone else was using this version with load balance strategy without having issue. Just to try to narrow down where the issue comes from: nifi 2.4 or our platform. Anyway thank you very much for your answer Andrés,   Best regards,   Olivier   ... View more