Recently there were several bug fixes in Google Drive processors and there is one more ongoing PR [1] which is an improvement but also contains a fix introduced in [2]. So at least this additional fix needs to be merged, otherwise there will be a regression in ListGoogleDrive. I can create a separate PR with the fix only if the whole PR review can not fit into the 2.3 timeline.
[1] https://github.com/apache/nifi/pull/9779 [2] https://issues.apache.org/jira/browse/NIFI-14291 Regards, Peter Turcsanyi On Thu, Mar 6, 2025 at 7:37 PM Matt Burgess <mattyb...@apache.org> wrote: > Joe, > > Good catch! I'm in favor of the revert since the processor works without > it. > > On Thu, Mar 6, 2025 at 1:31 PM Joe Gresock <jgres...@gmail.com> wrote: > > > I confirmed that [1] is an issue that prevents ListSFTP from returning > any > > more than the configured value in the Remote Poll Batch Size, even after > > multiple executions of the processor. While the workaround is to > increase > > the value of this property to a very high number, it seems problematic > > enough for me to warrant trying to get a fix into the 2.3 release. > > > > I have a working fix [2] that reverts [3] (NIFI-12772), essentially > > removing the Remote Poll Batch Size property again. What do we think > about > > trying to get this in before the release? > > > > This property could be implemented correctly, but it does not look like a > > simple fix to me, so I'd suggest reverting it instead of trying to > correct > > the implementation before 2.3. > > > > [1] https://issues.apache.org/jira/browse/NIFI-14326 > > [2] https://github.com/apache/nifi/pull/9782 > > [3] https://github.com/apache/nifi/pull/8390/files > > > > On Thu, Mar 6, 2025 at 12:12 PM David Handermann < > > exceptionfact...@apache.org> wrote: > > > > > Thanks initiating the discussion and planning to handle the Release > > Manager > > > responsibilities, Pierre! > > > > > > With a faster release cadence lately, I'm in favor of proceeding, and > I'm > > > not aware of any immediate blockers. Anything that is not quite ready > can > > > certainly be picked up soon in subsequent releases. > > > > > > Regards, > > > David Handermann > > > > > > On Wed, Mar 5, 2025, 3:18 AM Pierre Villard < > pierre.villard...@gmail.com > > > > > > wrote: > > > > > > > Team, > > > > > > > > The NiFi 2.3.0 version [1] has already 90 Jira issues resolved. There > > > > are also some PRs being actively reviewed that should be merged in > the > > > > next few days. I would like to consider starting a NiFi 2.3.0 release > > > > candidate build before the end of this week, and I'm happy to handle > > > > RM duties for the release. > > > > > > > > I will evaluate currently available dependency updates and file a PR > > > > later today. After that, we should be in a good position to move > > > > forward later this week. > > > > > > > > Let me know if there are specific PRs being actively reviewed that > > > > should be considered as a blocker before starting the process. > > > > > > > > Thanks, > > > > Pierre > > > > > > > > [1] https://issues.apache.org/jira/projects/NIFI/versions/12355600 > > > > > > > > > >
