Hi Jagadish,
I was able to verify the value for java.library.path in the init method.
It looks correct to me as includes the path to the directory where all the
dependent libraries are located.
Angelica
On 6/9/17, 11:01 AM, "Jagadish Venkatraman" wrote:
>Can you verify that the path that the
Can you verify that the path that the JVM tries to find the library
(present in the LinkageError) is valid and is a part of java.library.path ?
You can do this by printing `(System.getProperty("java.library.path"));`
inside your StreamTask's *init* method.
Best,
Jagadish
On Thu, Jun 8, 2017 at 9
Github user asfgit closed the pull request at:
https://github.com/apache/samza/pull/221
---
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 enabl
Github user asfgit closed the pull request at:
https://github.com/apache/samza/pull/222
---
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 enabl
GitHub user vjagadish1989 opened a pull request:
https://github.com/apache/samza/pull/222
Update release instructions to publish artifacts for different scala
versions
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vjagadish198
GitHub user logarithm opened a pull request:
https://github.com/apache/samza/pull/221
SAMZA-1331: Optimize Snapshot class constructor
In some of our workloads (where we need to gather samza metrics five times
per minute) `SlidingTimeWindowReservoir.getSnapshot()` method takes up to
