Github user HeartSaVioR commented on a diff in the pull request:

    https://github.com/apache/storm/pull/2443#discussion_r202638239
  
    --- Diff: 
sql/storm-sql-runtime/src/jvm/org/apache/storm/sql/runtime/datasource/socket/bolt/SocketBolt.java
 ---
    @@ -0,0 +1,108 @@
    +/*
    + * 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.storm.sql.runtime.datasource.socket.bolt;
    +
    +import java.io.BufferedWriter;
    +import java.io.IOException;
    +import java.io.OutputStreamWriter;
    +import java.net.Socket;
    +import java.util.Map;
    +
    +import org.apache.storm.shade.org.apache.commons.io.IOUtils;
    +import org.apache.storm.sql.runtime.IOutputSerializer;
    +import org.apache.storm.task.OutputCollector;
    +import org.apache.storm.task.TopologyContext;
    +import org.apache.storm.topology.IRichBolt;
    +import org.apache.storm.topology.OutputFieldsDeclarer;
    +import org.apache.storm.tuple.Tuple;
    +import org.apache.storm.tuple.Values;
    +import org.slf4j.Logger;
    +import org.slf4j.LoggerFactory;
    +
    +/**
    + * The Bolt implementation for Socket. Only available for Storm SQL.
    + * The class doesn't handle reconnection so you may not want to use this 
for production.
    --- End diff --
    
    You could do some experiments with your production query via replacing 
input table and/or output table to socket. 
    
    We may also want to have console output table (it can't be input table for 
sure) but we could address it from follow-up issue.
    
    Please refer others' cases: Spark has couple of input sources and output 
sinks for testing, whereas Flink doesn't look like providing table sources and 
table sinks for testing. I'd rather feel better on Spark for this case.
    
    
http://spark.apache.org/docs/latest/structured-streaming-programming-guide.html#input-sources
    
http://spark.apache.org/docs/latest/structured-streaming-programming-guide.html#output-sinks
    
    
https://ci.apache.org/projects/flink/flink-docs-release-1.5/dev/table/sourceSinks.html


---

Reply via email to