@Vasu_ While NiFi still generates a flow.xml.gz, it is no longer the file that is loaded during NiFi startup.  If the flow.json.gz file exists, that is what is going to be loaded.  So if you swap out only the flow.xml.gz with a flow.xml.gz from archive and do not remove the flow.json.gz, the flow.json.gz is still going to be loaded. When only the flow.xml.gz exists, NiFi will load it and convert it to a flow.json.gz which it will use from that point forward.  At this time, NiFi will still output both a flow.json.gs and flow.xml.gz as you make changes to the canvas in the NiFi UI.  Eventually the flow.xml.gz will go away completely.   If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt ... View more

@jisaitua  Definitely some weird unexpected behavior there. I was able to reproduce your issue, as well as some other unexpected behavior around same area. As a workaround to your specific issue, the following NiFi Expression Language (NEL) will get you what you are looking for: {${literal('')}"$${key}":"${literal('value')}"} I also filed an Apache NiFi jira for this issue: https://issues.apache.org/jira/browse/NIFI-11738   I reproduced on an Apache NiFi 1.18 cluster I have running, so it is not an issue that just recently appeared. If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt ... View more

@hule  Welcome to the community. I am not completely clear on your use case from your description.  What are you trying to accomplish? Are you trying to generate emails within NiFi and send to an external outlook email address or are trying to have your NiFi receive emails? It sounds like maybe sending an email from a NiFi dataflow to some email address.  If so, the processor you want to use is the putEmail processor.  As far as the SMTP settings, those need to come from the target SMTP server.   For example: Microsoft provides SMTP settings here: https://support.microsoft.com/en-gb/office/pop-imap-and-smtp-settings-8361e398-8af4-4e97-b147-6c6c4ac95353 Google Gmail provides SMTP settings here: https://support.google.com/a/answer/176600?hl=en If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt ... View more

@Kiranq  This is what I believe you executed from yoru description: You were originally using the the FileSystemFlowPersistenceProvider and has already version controlled one or more NiFi Process Groups (PG) to your NiFi-Registry? Then you change your configuration to use the GitFlowPersistenceProvider? This is what I believe you did not do: Prior to switching flow persistence providers, did you stop version control on all your PGs? Switching from other Flow Persistence Provider In order to switch the Flow Persistence Provider, it is necessary to reset NiFi Registry. For example, to switch from FileSystemFlowPersistenceProvider to GitFlowPersistenceProvider, follow these steps: Stop version control on all ProcessGroups in NiFi Stop NiFi Registry Move the H2 DB (specified as nifi.registry.db.directory in nifi-registry.properties) and Flow Storage Directory for FileSystemFlowPersistenceProvider directories somewhere for back up Configure GitFlowPersistenceProvider provider in providers.xml Start NiFi Registry Recreate any buckets Start version control on all ProcessGroups again. It appears as though you may not have followed the above documented steps in the NiFi-Registry admin guide (https://nifi.apache.org/docs/nifi-registry-docs/html/administration-guide.html#flow-persistence-providers).  This leaves you with your Metadata Database with info about your version controlled PGs and that metadata references flows persisted that it can no longer find in the flow persistence provider configured. If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt     ... View more