Yes this is best approach, Inserting all in staging table and then using merge to insert/update on target table, Just need to truncate staging table for next round of inserts.  ... View more

@Griggsy, Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.  ... View more

@mburgess I have the same problem. The code was written in jython.   from org.apache.commons.io import IOUtils from java.nio.charset import StandardCharsets from org.apache.nifi.processor.io import OutputStreamCallback from java.lang import Object # Define a subclass of OutputStreamCallback for use in session.write() class PyOutputStreamCallback(OutputStreamCallback):   def __init__(self, cadena):     self.cadena = cadena   def process(self, outputStream):     outputStream.write(bytearray(self.cadena.encode('utf-8'))) # end class flowFile = session.get() if (flowFile != None):     table = flowFile.getAttribute('table_name')         if (table != 'database_1.dbo.dtproperties'):         newFlowFile = session.create(flowFile)         newFFC = ''         newFlowFile = session.write(newFlowFile, PyOutputStreamCallback(newFFC))                 session.transfer(newFlowFile, REL_SUCCESS)             elif (table == 'database_1.dbo.dtproperties'):         session.remove(flowFile)     else:         session.transfer(flowFile, REL_FAILURE)   I'm understanding that flow files are passing one by one, right? So if there is a flow file with an attribute ''database_1.dbo.dtproperties" should be eliminated without affecting other flow files. But I got "flowfile has already marked for removal" ... View more

Hi @gkp_shakeel ,   Can you please help me with the CURSOR data type object and the INTERFACE_DATA%ROWTYPE; Parameters. How can I call such store procedure   ... View more

@kcc, as this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. ... View more

Agreed, you do not have access to the fields in either the incoming or outgoing JSON objects using Expression Language in the spec. ... View more

I believe the type checking for logical types is more strict now as of https://issues.apache.org/jira/browse/AVRO-2493 and NiFi 1.17.0 (when we upgraded to Avro 1.11.1). Are you using "int" or "string" as the normal Avro type? According the spec (https://avro.apache.org/docs/1.11.1/specification/#timestamp-millisecond-precision) it must be "long". ... View more

Try specifying schema with precision ex: {"type":"record","name":"schema","fields":[{"name":"_COL_0","type":{"type":"fixed","name":"_COL_0","size":16,"logicalType":"decimal","precision":38,"scale":0}}} ... View more

@Althotta As this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. Thanks! ... View more

@yamaga, as this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. ... View more