Re: Execute SQL support for nvarchar(max) datatype

2019-04-18 Thread Endre Kovács
Hi Venu, I belive it would only be possible if the PDF would be base64 encoded before DB insertion, and then in NiFi it would need to be base64 decoded. Seems possible, but adds a bit of computing overhead to the flow. Best regards, Endre On Thu, Apr 18, 2019, 5:09 PM Venugopal Iyengar wrote: >

Re: Execute SQL support for nvarchar(max) datatype

2019-04-18 Thread Venugopal Iyengar
Thanks Peter. We are trying to avoid using nvarchar going forward. However, for some schema it is implemented that way by some consultants. If you can give me the steps to debug that would be helpful. Is it possible to get this working by using some converters as part of the flow? I appreciate your

Re: Execute SQL support for nvarchar(max) datatype

2019-04-16 Thread Peter Turcsanyi
Hi Venu, If I'm not wrong, you're using MS SQL Server and nvarchar / varbinary are the database column types. nvarchar can be used for storing character data (strings) but it is not suitable for binary data (like pdf). I think NiFi tries to handle the bytes of the pdf file as Unicode characters.

Execute SQL support for nvarchar(max) datatype

2019-04-15 Thread Venugopal Iyengar
Hello there, I am using Execute SQL, Split AVro and put file processors to read some pdf documents stored in SQL database and store that in the file system. When I use varbinary(max) I was able to pull and view the pdf without any issues. When the datatype is nvarchar(max) I am unable to open t