[GitHub] nifi pull request: NIFI-631 Create ListFile and FetchFile processo...

[jskora]

Github user jskora closed the pull request at:

https://github.com/apache/nifi/pull/112


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: NIFI-869 Fixed formatting issue

[olegz]

Github user olegz commented on the pull request:

https://github.com/apache/nifi/pull/110#issuecomment-152734921
  
Pushed to the trunk


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: NIFI-869 Fixed formatting issue

[olegz]

Github user olegz closed the pull request at:

https://github.com/apache/nifi/pull/110


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

LogAttribute - Sending that output to a custom logger?

[Mark Petronic]

>From the code, it appears it cannot be done as the attribute logging
goes the same getLogger() instance as the normal nifi-app traces. Has
anyone considered making that configurable, maybe allowing you do
define a different logger name for LogAttribute then creating that
logger definition in log back conf allowing flexibility? I'm using
attribute logging heavily as I try to better learn/debug Nifi (it give
you a nice 'under the hood' view of the flow) and build up some flows
and feel it would be beneficial to be able to capture the LogAttribte
message by themselves for more clarity on what is happening. I would
not mind maybe trying to implement this feature as my first crack at
contributing to the project. Seems like a fairly easy one that would
allow me to "go through the motions" of a full pull request process
and iron out the process. Anyone have any thoughts on this?

Re: Constant "Cleanup Archive for default" log messages

[Mark Payne]

Mark,

That's my bad. I added some debug logging recently and logged that at the INFO
level. It will be addressed in NIFI-1090 [1].

Thanks
-Mark

[1] https://issues.apache.org/jira/browse/NIFI-1090 



> On Oct 31, 2015, at 2:45 AM, Mark Petronic  wrote:
> 
> I just built off commit 5cc2b04b918a0a3c76c0f1d71c7a416d0dce3f39 with this
> pulled in on top of that commit: https://github.com/jskora/nifi NIFI-631,
> and I see these log message constantly appearing after I updated my
> installation. Anyone know what would cause this? I did not see this when I
> installed the 0.3.0 release. Note that I also increase the logical volume
> where the content repo was from 100G to 250G, if that matters.
> 
> 2015-10-31 06:38:58,118 INFO [Cleanup Archive for default]
> o.a.n.c.r.F.archive.expiration Currently 250596823040 bytes free for
> Container default; requirement is 137324361973 byte free, so need to free
> -113272461067 bytes
> 2015-10-31 06:38:59,129 INFO [Cleanup Archive for default]
> o.a.n.c.r.F.archive.expiration Currently 250596823040 bytes free for
> Container default; requirement is 137324361973 byte free, so need to free
> -113272461067 bytes
> 2015-10-31 06:39:00,141 INFO [Cleanup Archive for default]
> o.a.n.c.r.F.archive.expiration Currently 250596823040 bytes free for
> Container default; requirement is 137324361973 byte free, so need to free
> -113272461067 bytes
> 2015-10-31 06:39:01,152 INFO [Cleanup Archive for default]
> o.a.n.c.r.F.archive.expiration Currently 250596823040 bytes free for
> Container default; requirement is 137324361973 byte free, so need to free
> -113272461067 bytes
> 2015-10-31 06:39:02,163 INFO [Cleanup Archive for default]
> o.a.n.c.r.F.archive.expiration Currently 250596823040 bytes free for
> Container default; requirement is 137324361973 byte free, so need to free
> -113272461067 bytes
> 2015-10-31 06:39:03,175 INFO [Cleanup Archive for default]
> o.a.n.c.r.F.archive.expiration Currently 250596823040 bytes free for
> Container default; requirement is 137324361973 byte free, so need to free
> -113272461067 bytes