True that. I'm an IRC fan too, just sharing other options :) Sent from my iPhone
> On Nov 8, 2015, at 5:12 PM, Tony Kurc <[email protected]> wrote: > > there is a set of people that will always associate irc with open source > software development projects. I don't mind lurking and redirecting people. > >> On Sun, Nov 8, 2015 at 12:53 PM, Matt Burgess <[email protected]> wrote: >> Would we have more participation with something like a Slack team? Apache >> Drill has one with #user and #dev channels, seems to work pretty well and >> has various integrations with other tools (email, GitHub, Jira, etc.) >> >> Sent from my iPhone >> >>> On Nov 8, 2015, at 12:41 PM, Tony Kurc <[email protected]> wrote: >>> >>> The irc channel tends to me be or Josh Elser redirecting people to the >>> mailing lists for memorialization. >>> >>>> On Sun, Nov 8, 2015 at 12:35 PM, Joe Witt <[email protected]> wrote: >>>> Aldrin - regarding IRC [1] >>>> >>>> We definitely need to get this info up on the website. >>>> >>>> [1] >>>> http://mail-archives.apache.org/mod_mbox/nifi-dev/201411.mbox/%3CCA%2BLyY57QFsxDxrHoNX7PGHd%2BFvX3ymQ%3DM8OtDnYxNeZEg3pAsA%40mail.gmail.com%3E >>>> >>>> Thanks >>>> Joe >>>> >>>> On Sun, Nov 8, 2015 at 12:31 PM, Aldrin Piri <[email protected]> wrote: >>>> > Mild tangent. I vaguely remember it coming up on the mailing list quite >>>> > some time ago, but is the IRC channel's information available anywhere on >>>> > the site? Wasn't able to find anything immediately obvious. >>>> > >>>> > On Sun, Nov 8, 2015 at 12:19 PM, Tony Kurc <[email protected]> wrote: >>>> >> >>>> >> and a proxy from irc answer: >>>> >> >>>> >> Anyway, I did search the mail lists and >>>> >> figured out how to get things working. >>>> >> In order to help anyone else out how might now know, here's a >>>> >> useful way to google the mail lists: >>>> >> >>>> >> https://www.google.com/webhp?q=site:http:%2F%2Fmail-archives.apache.org%2Fmod_mbox%2Fkafka-users%2F#q=site:http:%2F%2Fmail-archives.apache.org%2Fmod_mbox%2Fnifi-users%2F >>>> >> >>>> >> Also it turns out that doing what I needed to do (wrapping the >>>> >> message in a base64-encoded string) was not that difficult, >>>> >> using >>>> >> the ExecuteStreamCommand processor, calling a simple BASH >>>> >> script >>>> >> which used "read" to loop through each line of the >>>> >> FlowFile. >>>> >> >>>> >> >>>> >> On Sun, Nov 8, 2015 at 8:09 AM, Tony Kurc <[email protected]> wrote: >>>> >>> >>>> >>> " I'd appreciate it if someone could tell me how to easily change a >>>> >>> flow >>>> >>> with JSON >>>> >>> lines like {JSON} to {"x"={JSON}} . The ReplaceText processor >>>> >>> seems like the right thing, but when I add almost anything to the >>>> >>> ReplacementValue field to change the output, it causes problems >>>> >>> and doesn't include the new literal text, or drops the matching >>>> >>> group altogether, showing $1 as a literal." >>>> >>> >>>> >> >>>> > >
