Apache NiFi contributor access
Hi, I would like to get contributor access to Apache Nifi on JIRA. Can you please add me to contributor list? My username is SatwikB. Thanks, Satwik
Re: Think I hit a regression in the record api
Is there a unit test for that?
On December 10, 2018 at 12:05:22, Mike Thomsen (mikerthom...@gmail.com)
wrote:
Schema:
{
"type": "record",
"name": "TSTest",
"fields": [
{ "name": "uuid", "type":"string" },
{ "name": "ts", "type": { "type": "long", "logicalType":
"timestamp-millis" }}
]
}
Example input:
{
"uuid": "4e64ce00-e6cc-492c-a4d6-57d3f43c4101",
"ts": 1544460087689
}
I had a JsonTreeReader set on PutElasticSearchHttpRecord, and it used the
format below:
-MM-dd'T'HH:mm:ss'Z'
ElasticSearch reported invalid input, and when I looked at the output being
sent to Elastic it appeared to be hard set to use -MM-dd HH:mm:ss
I added that format to the date field in Elastic, and Elastic was happy
with the input.
Best I can tell, it appears that in 1.8 it's ignoring the user-supplied
timestamp formatter.
Think I hit a regression in the record api
Schema:
{
"type": "record",
"name": "TSTest",
"fields": [
{ "name": "uuid", "type":"string" },
{ "name": "ts", "type": { "type": "long", "logicalType":
"timestamp-millis" }}
]
}
Example input:
{
"uuid": "4e64ce00-e6cc-492c-a4d6-57d3f43c4101",
"ts": 1544460087689
}
I had a JsonTreeReader set on PutElasticSearchHttpRecord, and it used the
format below:
-MM-dd'T'HH:mm:ss'Z'
ElasticSearch reported invalid input, and when I looked at the output being
sent to Elastic it appeared to be hard set to use -MM-dd HH:mm:ss
I added that format to the date field in Elastic, and Elastic was happy
with the input.
Best I can tell, it appears that in 1.8 it's ignoring the user-supplied
timestamp formatter.
Re: [DISCUSS] Early, voluntary relocation to GitBox
+1 as well, should ease the contribution workflow. Thanks for volunteering Aldrin. Le lun. 10 déc. 2018 à 16:41, Laszlo Horvath a écrit : > +1 > > On 10/12/2018, 15:22, "Michael Moser" wrote: > > +1 from me, sounds great. > > > On Mon, Dec 10, 2018 at 4:07 AM Arpad Boda > wrote: > > > +1 (for being the guinea pig __ ) > > > > On 09/12/2018, 04:01, "Aldrin Piri" wrote: > > > > Thanks to those of you that responded. > > > > I think my tentative plan is to give this a few more days to see > if > > there > > are any strong objections. Otherwise, I'll look to file the > ticket > > around > > midweek and then look to begin the process toward the end of > next week > > to > > hopefully minimize disruptions. Thanks again! > > > > On Sat, Dec 8, 2018 at 12:09 PM Tony Kurc > wrote: > > > > > +1, sounds like a great idea > > > > > > On Sat, Dec 8, 2018 at 7:44 AM Mike Thomsen < > mikerthom...@gmail.com> > > > wrote: > > > > > > > +1 > > > > > > > > On Fri, Dec 7, 2018 at 9:08 PM Sivaprasanna < > > sivaprasanna...@gmail.com> > > > > wrote: > > > > > > > > > +1 (non-binding) > > > > > > > > > > I’m in. Thanks for doing it, Aldrin. > > > > > > > > > > > > > > > On Sat, 8 Dec 2018 at 7:32 AM, James Wing < > jvw...@gmail.com> > > wrote: > > > > > > > > > > > +1, thanks for volunteering. > > > > > > > > > > > > > On Dec 7, 2018, at 13:39, Kevin Doran < > > kdoran.apa...@gmail.com> > > > > wrote: > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > On 12/7/18, 15:17, "Andy LoPresto" < > alopre...@apache.org> > > wrote: > > > > > > > > > > > > > >+1. > > > > > > > > > > > > > >Andy LoPresto > > > > > > >alopre...@apache.org > > > > > > >alopresto.apa...@gmail.com > > > > > > >PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE > 3C6E F65B > > 2F7D > > > > EF69 > > > > > > > > > > > > > >> On Dec 7, 2018, at 11:11 AM, Aldrin Piri < > > aldrinp...@gmail.com> > > > > > wrote: > > > > > > >> > > > > > > >> Hey folks, > > > > > > >> > > > > > > >> Daniel Gruno sent an email to the dev list about the > > deprecation > > > of > > > > > our > > > > > > >> git-wip repositories [1] (these are the canonical > repos that > > > > > committers > > > > > > >> push changes to and are currently mirrored to GitHub) > and > > > > > transitioning > > > > > > to > > > > > > >> GitBox [2]. > > > > > > >> > > > > > > >> As highlighted in that email, this will not be an > optional > > change, > > > > > only > > > > > > in > > > > > > >> when and how it happens. There was a previous > discussion > > over > > > this > > > > > > topic > > > > > > >> [3] where it was generally well received but I think > some > > of the > > > > > > logistics > > > > > > >> were never mapped out and thus the actual request to > do so > > was > > > never > > > > > > >> executed. > > > > > > >> > > > > > > >> I am proposing we volunteer for the early > relocation. The > > process > > > > > > looks to > > > > > > >> be fairly straightforward and should ultimately only > result > > in > > > > > requiring > > > > > > >> our contributors to add/replace their original > git-wip based > > > > remotes. > > > > > > >> > > > > > > >> If folks are in favor, I am happy to file the > requisite > > INFRA > > > ticket > > > > > and > > > > > > >> provide the associated communication/docs to the > community > > to make > > > > > this > > > > > > >> happen. Again, this is only about making the choice > to > > perform > > > this > > > > > > >> migration now, in a coordinated manner, in lieu of > the mass > > > > migration > > > > > > that > > > > > > >> would happen later. > > > > > > >> > > > > > > >> From a project management standpoint, I think it is a > nice > > bit of > > > > > > >> functionality that lets us better curate our open PRs > and, > > given > > > my > > > > > > prior > > > > > > >> interest in the subject, would like to see it happen. > > > > > > >> > > > > > > >> --aldrin > > > > > > >> > > > > > > >> [1] > > > > > > >> > > > > > > > > > > > > > > > > > > > > > https://lists.apache.org/thread.html/8247bb17671d6131b1d7a646b4c018b21
Re: [DISCUSS] Early, voluntary relocation to GitBox
+1 On 10/12/2018, 15:22, "Michael Moser" wrote: +1 from me, sounds great. On Mon, Dec 10, 2018 at 4:07 AM Arpad Boda wrote: > +1 (for being the guinea pig __ ) > > On 09/12/2018, 04:01, "Aldrin Piri" wrote: > > Thanks to those of you that responded. > > I think my tentative plan is to give this a few more days to see if > there > are any strong objections. Otherwise, I'll look to file the ticket > around > midweek and then look to begin the process toward the end of next week > to > hopefully minimize disruptions. Thanks again! > > On Sat, Dec 8, 2018 at 12:09 PM Tony Kurc wrote: > > > +1, sounds like a great idea > > > > On Sat, Dec 8, 2018 at 7:44 AM Mike Thomsen > > wrote: > > > > > +1 > > > > > > On Fri, Dec 7, 2018 at 9:08 PM Sivaprasanna < > sivaprasanna...@gmail.com> > > > wrote: > > > > > > > +1 (non-binding) > > > > > > > > I’m in. Thanks for doing it, Aldrin. > > > > > > > > > > > > On Sat, 8 Dec 2018 at 7:32 AM, James Wing > wrote: > > > > > > > > > +1, thanks for volunteering. > > > > > > > > > > > On Dec 7, 2018, at 13:39, Kevin Doran < > kdoran.apa...@gmail.com> > > > wrote: > > > > > > > > > > > > +1 > > > > > > > > > > > > On 12/7/18, 15:17, "Andy LoPresto" > wrote: > > > > > > > > > > > >+1. > > > > > > > > > > > >Andy LoPresto > > > > > >alopre...@apache.org > > > > > >alopresto.apa...@gmail.com > > > > > >PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B > 2F7D > > > EF69 > > > > > > > > > > > >> On Dec 7, 2018, at 11:11 AM, Aldrin Piri < > aldrinp...@gmail.com> > > > > wrote: > > > > > >> > > > > > >> Hey folks, > > > > > >> > > > > > >> Daniel Gruno sent an email to the dev list about the > deprecation > > of > > > > our > > > > > >> git-wip repositories [1] (these are the canonical repos that > > > > committers > > > > > >> push changes to and are currently mirrored to GitHub) and > > > > transitioning > > > > > to > > > > > >> GitBox [2]. > > > > > >> > > > > > >> As highlighted in that email, this will not be an optional > change, > > > > only > > > > > in > > > > > >> when and how it happens. There was a previous discussion > over > > this > > > > > topic > > > > > >> [3] where it was generally well received but I think some > of the > > > > > logistics > > > > > >> were never mapped out and thus the actual request to do so > was > > never > > > > > >> executed. > > > > > >> > > > > > >> I am proposing we volunteer for the early relocation. The > process > > > > > looks to > > > > > >> be fairly straightforward and should ultimately only result > in > > > > requiring > > > > > >> our contributors to add/replace their original git-wip based > > > remotes. > > > > > >> > > > > > >> If folks are in favor, I am happy to file the requisite > INFRA > > ticket > > > > and > > > > > >> provide the associated communication/docs to the community > to make > > > > this > > > > > >> happen. Again, this is only about making the choice to > perform > > this > > > > > >> migration now, in a coordinated manner, in lieu of the mass > > > migration > > > > > that > > > > > >> would happen later. > > > > > >> > > > > > >> From a project management standpoint, I think it is a nice > bit of > > > > > >> functionality that lets us better curate our open PRs and, > given > > my > > > > > prior > > > > > >> interest in the subject, would like to see it happen. > > > > > >> > > > > > >> --aldrin > > > > > >> > > > > > >> [1] > > > > > >> > > > > > > > > > > > > > > > https://lists.apache.org/thread.html/8247bb17671d6131b1d7a646b4c018b21aac390c4f627d8fb1f421b2@%3Cdev.nifi.apache.org%3E > > > > > >> [2] https://gitbox.apache.org/ > > > > > >> [3] > > > > > >> > > > > > > > > > > > > > > > https://lists.apache.org/thread.html/de5e103994f356b1b8a572410938eef44af8cb352210e35305c04bc9@%3Cdev.nifi.apache.org%3E > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: [DISCUSS] Early, voluntary relocation to GitBox
+1 from me, sounds great. On Mon, Dec 10, 2018 at 4:07 AM Arpad Boda wrote: > +1 (for being the guinea pig __ ) > > On 09/12/2018, 04:01, "Aldrin Piri" wrote: > > Thanks to those of you that responded. > > I think my tentative plan is to give this a few more days to see if > there > are any strong objections. Otherwise, I'll look to file the ticket > around > midweek and then look to begin the process toward the end of next week > to > hopefully minimize disruptions. Thanks again! > > On Sat, Dec 8, 2018 at 12:09 PM Tony Kurc wrote: > > > +1, sounds like a great idea > > > > On Sat, Dec 8, 2018 at 7:44 AM Mike Thomsen > > wrote: > > > > > +1 > > > > > > On Fri, Dec 7, 2018 at 9:08 PM Sivaprasanna < > sivaprasanna...@gmail.com> > > > wrote: > > > > > > > +1 (non-binding) > > > > > > > > I’m in. Thanks for doing it, Aldrin. > > > > > > > > > > > > On Sat, 8 Dec 2018 at 7:32 AM, James Wing > wrote: > > > > > > > > > +1, thanks for volunteering. > > > > > > > > > > > On Dec 7, 2018, at 13:39, Kevin Doran < > kdoran.apa...@gmail.com> > > > wrote: > > > > > > > > > > > > +1 > > > > > > > > > > > > On 12/7/18, 15:17, "Andy LoPresto" > wrote: > > > > > > > > > > > >+1. > > > > > > > > > > > >Andy LoPresto > > > > > >alopre...@apache.org > > > > > >alopresto.apa...@gmail.com > > > > > >PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B > 2F7D > > > EF69 > > > > > > > > > > > >> On Dec 7, 2018, at 11:11 AM, Aldrin Piri < > aldrinp...@gmail.com> > > > > wrote: > > > > > >> > > > > > >> Hey folks, > > > > > >> > > > > > >> Daniel Gruno sent an email to the dev list about the > deprecation > > of > > > > our > > > > > >> git-wip repositories [1] (these are the canonical repos that > > > > committers > > > > > >> push changes to and are currently mirrored to GitHub) and > > > > transitioning > > > > > to > > > > > >> GitBox [2]. > > > > > >> > > > > > >> As highlighted in that email, this will not be an optional > change, > > > > only > > > > > in > > > > > >> when and how it happens. There was a previous discussion > over > > this > > > > > topic > > > > > >> [3] where it was generally well received but I think some > of the > > > > > logistics > > > > > >> were never mapped out and thus the actual request to do so > was > > never > > > > > >> executed. > > > > > >> > > > > > >> I am proposing we volunteer for the early relocation. The > process > > > > > looks to > > > > > >> be fairly straightforward and should ultimately only result > in > > > > requiring > > > > > >> our contributors to add/replace their original git-wip based > > > remotes. > > > > > >> > > > > > >> If folks are in favor, I am happy to file the requisite > INFRA > > ticket > > > > and > > > > > >> provide the associated communication/docs to the community > to make > > > > this > > > > > >> happen. Again, this is only about making the choice to > perform > > this > > > > > >> migration now, in a coordinated manner, in lieu of the mass > > > migration > > > > > that > > > > > >> would happen later. > > > > > >> > > > > > >> From a project management standpoint, I think it is a nice > bit of > > > > > >> functionality that lets us better curate our open PRs and, > given > > my > > > > > prior > > > > > >> interest in the subject, would like to see it happen. > > > > > >> > > > > > >> --aldrin > > > > > >> > > > > > >> [1] > > > > > >> > > > > > > > > > > > > > > > https://lists.apache.org/thread.html/8247bb17671d6131b1d7a646b4c018b21aac390c4f627d8fb1f421b2@%3Cdev.nifi.apache.org%3E > > > > > >> [2] https://gitbox.apache.org/ > > > > > >> [3] > > > > > >> > > > > > > > > > > > > > > > https://lists.apache.org/thread.html/de5e103994f356b1b8a572410938eef44af8cb352210e35305c04bc9@%3Cdev.nifi.apache.org%3E > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: [DISCUSS] Early, voluntary relocation to GitBox
+1 (for being the guinea pig __ ) On 09/12/2018, 04:01, "Aldrin Piri" wrote: Thanks to those of you that responded. I think my tentative plan is to give this a few more days to see if there are any strong objections. Otherwise, I'll look to file the ticket around midweek and then look to begin the process toward the end of next week to hopefully minimize disruptions. Thanks again! On Sat, Dec 8, 2018 at 12:09 PM Tony Kurc wrote: > +1, sounds like a great idea > > On Sat, Dec 8, 2018 at 7:44 AM Mike Thomsen > wrote: > > > +1 > > > > On Fri, Dec 7, 2018 at 9:08 PM Sivaprasanna > > wrote: > > > > > +1 (non-binding) > > > > > > I’m in. Thanks for doing it, Aldrin. > > > > > > > > > On Sat, 8 Dec 2018 at 7:32 AM, James Wing wrote: > > > > > > > +1, thanks for volunteering. > > > > > > > > > On Dec 7, 2018, at 13:39, Kevin Doran > > wrote: > > > > > > > > > > +1 > > > > > > > > > > On 12/7/18, 15:17, "Andy LoPresto" wrote: > > > > > > > > > >+1. > > > > > > > > > >Andy LoPresto > > > > >alopre...@apache.org > > > > >alopresto.apa...@gmail.com > > > > >PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D > > EF69 > > > > > > > > > >> On Dec 7, 2018, at 11:11 AM, Aldrin Piri > > > wrote: > > > > >> > > > > >> Hey folks, > > > > >> > > > > >> Daniel Gruno sent an email to the dev list about the deprecation > of > > > our > > > > >> git-wip repositories [1] (these are the canonical repos that > > > committers > > > > >> push changes to and are currently mirrored to GitHub) and > > > transitioning > > > > to > > > > >> GitBox [2]. > > > > >> > > > > >> As highlighted in that email, this will not be an optional change, > > > only > > > > in > > > > >> when and how it happens. There was a previous discussion over > this > > > > topic > > > > >> [3] where it was generally well received but I think some of the > > > > logistics > > > > >> were never mapped out and thus the actual request to do so was > never > > > > >> executed. > > > > >> > > > > >> I am proposing we volunteer for the early relocation. The process > > > > looks to > > > > >> be fairly straightforward and should ultimately only result in > > > requiring > > > > >> our contributors to add/replace their original git-wip based > > remotes. > > > > >> > > > > >> If folks are in favor, I am happy to file the requisite INFRA > ticket > > > and > > > > >> provide the associated communication/docs to the community to make > > > this > > > > >> happen. Again, this is only about making the choice to perform > this > > > > >> migration now, in a coordinated manner, in lieu of the mass > > migration > > > > that > > > > >> would happen later. > > > > >> > > > > >> From a project management standpoint, I think it is a nice bit of > > > > >> functionality that lets us better curate our open PRs and, given > my > > > > prior > > > > >> interest in the subject, would like to see it happen. > > > > >> > > > > >> --aldrin > > > > >> > > > > >> [1] > > > > >> > > > > > > > > > > https://lists.apache.org/thread.html/8247bb17671d6131b1d7a646b4c018b21aac390c4f627d8fb1f421b2@%3Cdev.nifi.apache.org%3E > > > > >> [2] https://gitbox.apache.org/ > > > > >> [3] > > > > >> > > > > > > > > > > https://lists.apache.org/thread.html/de5e103994f356b1b8a572410938eef44af8cb352210e35305c04bc9@%3Cdev.nifi.apache.org%3E > > > > > > > > > > > > > > > > > > > >
