Could ve a good idea to log values at TRACE level then.
On Wed, Feb 27, 2019, 7:56 AM Matt Burgess wrote:
> True, at a DEBUG level we could output the record values, although for
> large flow files this will be quite verbose :) Also the point of the
> ?s is not necessarily to not show the
True, at a DEBUG level we could output the record values, although for
large flow files this will be quite verbose :) Also the point of the
?s is not necessarily to not show the values, but that we are
technically only issuing one statement (i.e. PreparedStatement), and
just the values change.
I could be mistaken, but I think that's standard JDBC behavior to not show
the values. That said, yes it would be a fairly trivial improvement to add
a dump of the record to a debug logger.
On Wed, Feb 27, 2019 at 4:36 AM Fred Affini
wrote:
> Hi Matt and Phillip, thanks a lot for the help
>
>
Hi Matt and Phillip, thanks a lot for the help
Setting PutDatabaseRecord log level to DEBUG (changing Bulletin Level in the
GUI or insert the XML line Matt sent) almost gave me what I need, the log
nos show:
10:32:55 CETDEBUGadcd1a7d-1000-1169-8aa8-92d8f2e891e5
Fred,
Sorry for the confusion, but I meant the log level on the PutDatabaseRecord
processor should be set to Debug.
Phillip
On Tue, Feb 26, 2019 at 11:32 AM Fred Affini
wrote:
> Hi Phillip, thanks for the reply.
>
> All my relationships (success, failure, retry) from PutDatabaseRecord are
>
Fred,
Try adding the following line to conf/logback.xml (somewhere around
line 88 where the other special processor levels are set :P)
Regards,
Matt
On Tue, Feb 26, 2019 at 11:32 AM Fred Affini wrote:
>
> Hi Phillip, thanks for the reply.
>
> All my relationships (success, failure, retry)
Hi Phillip, thanks for the reply.
All my relationships (success, failure, retry) from PutDatabaseRecord are
point to an LogAttribute processor.
On the properties of LogAttribute I have:
Log Level = debug
Attributes to Log = statement.type
What I got on bulletin board is:
17:29:31 CET WARNING
Fred,
Set the log level to debug and it should show on the bulletin. If you are
using the "Use statement.type Attribute", use the LogAttribute processor to
report the sql attribute. Phillip https://nifi.rocks
On Tue, Feb 26, 2019 at 8:30 AM fredaffini
wrote:
> Hello,
>
> Iam new to NiFi and
