Ah yea, take a look at RedisDistributedMapCacheClientService, that one
is closer to what you need.
Something like
RedisConnectionPool redisConnectionPool =
context.getProperty(REDIS_CONNECTION_POOL).asControllerService(RedisConnectionPool.class);
RedisConnection redisConnection =
Yeah, it does. Copied withConnection from the state provider. Looks like
copya pasta may have struck again...
On Mon, Mar 26, 2018 at 11:44 AM, Bryan Bende wrote:
> I can't tell for sure, but the stacktrace looks like your
> AbstractRedisProcessor is making a direct call to
https://github.com/MikeThomsen/nifi/commit/dad71af803a9ead5bcbead3ce65671c4c2430605#diff-09d6acf9b469f7d2491ab7dbdab93fea
On Mon, Mar 26, 2018 at 11:38 AM, Bryan Bende wrote:
> Can you share the code for your AbstractRedisProcessor?
>
>
> On Mon, Mar 26, 2018 at 9:52 AM, Mike
I can't tell for sure, but the stacktrace looks like your
AbstractRedisProcessor is making a direct call to RedisUtils to create
a connection, rather than using the RedisConnectionPool to obtain a
connection.
On Mon, Mar 26, 2018 at 11:38 AM, Bryan Bende wrote:
> Can you share
Can you share the code for your AbstractRedisProcessor?
On Mon, Mar 26, 2018 at 9:52 AM, Mike Thomsen wrote:
> Over the weekend I started playing around with a new processor called
> PutRedisHash based on a request from the user list. I set up a really
> simple IT and
Over the weekend I started playing around with a new processor called
PutRedisHash based on a request from the user list. I set up a really
simple IT and hit a problem pretty quickly. This passes validation:
@Test
public void testStandalone() throws Exception {
final String attrName =