flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From subhankarb <...@git.apache.org>
Subject [GitHub] flink pull request #1813: [FLINK-3034] Redis Sink Connector
Date Mon, 27 Jun 2016 10:10:09 GMT
Github user subhankarb commented on a diff in the pull request:

    https://github.com/apache/flink/pull/1813#discussion_r68551999
  
    --- Diff: flink-streaming-connectors/flink-connector-redis/src/main/java/org/apache/flink/streaming/connectors/redis/common/container/RedisContainer.java
---
    @@ -0,0 +1,219 @@
    +/*
    + * Licensed to the Apache Software Foundation (ASF) under one or more
    + * contributor license agreements.  See the NOTICE file distributed with
    + * this work for additional information regarding copyright ownership.
    + * The ASF licenses this file to You under the Apache License, Version 2.0
    + * (the "License"); you may not use this file except in compliance with
    + * the License.  You may obtain a copy of the License at
    + *
    + *    http://www.apache.org/licenses/LICENSE-2.0
    + *
    + * Unless required by applicable law or agreed to in writing, software
    + * distributed under the License is distributed on an "AS IS" BASIS,
    + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    + * See the License for the specific language governing permissions and
    + * limitations under the License.
    + */
    +package org.apache.flink.streaming.connectors.redis.common.container;
    +
    +import org.apache.flink.util.Preconditions;
    +import org.slf4j.Logger;
    +import org.slf4j.LoggerFactory;
    +import redis.clients.jedis.Jedis;
    +import redis.clients.jedis.JedisPool;
    +import redis.clients.jedis.JedisSentinelPool;
    +
    +import java.io.Closeable;
    +import java.io.IOException;
    +
    +/**
    + * Redis command container if we want to connect to a single Redis server or to Redis
sentinels
    + * If want to connect to a single Redis server, plz use the first constructor {@link
#RedisContainer(JedisPool)}.
    + * If want to connect to a Redis sentinels, Plz use the second constructor {@link #RedisContainer(JedisSentinelPool)}
    + */
    +public class RedisContainer implements RedisCommandsContainer, Closeable {
    +
    +	private static final long serialVersionUID = 1L;
    +
    +	private static final Logger LOG = LoggerFactory.getLogger(RedisContainer.class);
    +
    +	private JedisPool jedisPool;
    +	private JedisSentinelPool jedisSentinelPool;
    +
    +
    +	/**
    +	 * Use this constructor if to connect with single Redis server.
    +	 *
    +	 * @param jedisPool JedisPool which actually manages Jedis instances
    +	 */
    +	public RedisContainer(JedisPool jedisPool) {
    +		Preconditions.checkNotNull(jedisPool, "Jedis Pool can not be null");
    +		this.jedisPool = jedisPool;
    +	}
    +
    +	/**
    +	 * Use this constructor if Redis environment is clustered with sentinels.
    +	 *
    +	 * @param sentinelPool SentinelPool which actually manages Jedis instances
    +	 */
    +	public RedisContainer(final JedisSentinelPool sentinelPool) {
    +		Preconditions.checkNotNull(sentinelPool, "Jedis Sentinel Pool can not be null");
    +		this.jedisSentinelPool = sentinelPool;
    +	}
    +
    +	/**
    +	 * Closes the Jedis instances.
    +	 */
    +	@Override
    +	public void close() throws IOException {
    +		if (this.jedisPool != null) {
    +			this.jedisPool.close();
    +		}
    +		if (this.jedisSentinelPool != null) {
    +			this.jedisSentinelPool.close();
    +		}
    +	}
    +
    +	@Override
    +	public void hset(final String hashName, final String key, final String value) {
    +		Jedis jedis = null;
    +		try {
    +			jedis = getInstance();
    +			jedis.hset(hashName, key, value);
    --- End diff --
    
    The `RedisDataTypeDescription.additionalKey` is used for the key. Yah the param names
are confusing. i am making the changes according to the same line the client. Thank you very
much. :) 


---
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 enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message