> Sent: Tuesday, January 28, 2020 1:27 AM
> To: dev@samza.apache.org
> Subject: Re: Nullpointer After Upgrade from samza 1.0.0 to 1.3.0
>
> Thanks for sharing Jeremiah. The infringing code is calling listFiles on
> every file in the base directory, and since you'd configured that to b
: Tuesday, January 28, 2020 1:27 AM
To: dev@samza.apache.org
Subject: Re: Nullpointer After Upgrade from samza 1.0.0 to 1.3.0
Thanks for sharing Jeremiah. The infringing code is calling listFiles on
every file in the base directory, and since you'd configured that to be the
current directory of th
m: Brett Konold
> Sent: Thursday, January 23, 2020 3:45 PM
> To: Prateek Maheshwari
> Cc: dev@samza.apache.org
> Subject: Re: Nullpointer After Upgrade from samza 1.0.0 to 1.3.0
>
> Hey Jeremiah,
>
> It looks like TransactionalStateTaskStorageManager.removeOldCheckpoints is
> r
3:45 PM
To: Prateek Maheshwari
Cc: dev@samza.apache.org
Subject: Re: Nullpointer After Upgrade from samza 1.0.0 to 1.3.0
Hey Jeremiah,
It looks like TransactionalStateTaskStorageManager.removeOldCheckpoints is
relying on an assumption that the store directory actually has some
contents, which may
Hey Jeremiah,
It looks like TransactionalStateTaskStorageManager.removeOldCheckpoints is
relying on an assumption that the store directory actually has some
contents, which may not be true depending on the type of store being used.
Can you let me know what kind of KeyValueStore you've configured
Brett, can you take a look at this?
- Prateek
On Wed, Jan 15, 2020 at 9:41 AM Jeremiah Adams
wrote:
> I am updating our jobs to use samza 1.3.0. I'm getting a null pointer when
> manually committing via taskCoordinator.commit().
>
>
> Below is the stack trace - can anyone point me in the right
I am updating our jobs to use samza 1.3.0. I'm getting a null pointer when
manually committing via taskCoordinator.commit().
Below is the stack trace - can anyone point me in the right direction?
Thanks.
2020-01-15 10:33:35 RunLoop [ERROR] Task Partition 0 commit failed
java.lang.NullPointerE
