From issues-return-204247-archive-asf-public=cust-asf.ponee.io@spark.apache.org Mon Oct 8 05:54:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 0723018064E for ; Mon, 8 Oct 2018 05:54:04 +0200 (CEST) Received: (qmail 50669 invoked by uid 500); 8 Oct 2018 03:54:03 -0000 Mailing-List: contact issues-help@spark.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@spark.apache.org Received: (qmail 50660 invoked by uid 99); 8 Oct 2018 03:54:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Oct 2018 03:54:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 184A71A0817 for ; Mon, 8 Oct 2018 03:54:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id NB5ApY5pTNhC for ; Mon, 8 Oct 2018 03:54:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id B09345F35B for ; Mon, 8 Oct 2018 03:54:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id BD806E070F for ; Mon, 8 Oct 2018 03:54:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 53C2C247CB for ; Mon, 8 Oct 2018 03:54:00 +0000 (UTC) Date: Mon, 8 Oct 2018 03:54:00 +0000 (UTC) From: "Jungtaek Lim (JIRA)" To: issues@spark.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SPARK-24630) SPIP: Support SQLStreaming in Spark MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SPARK-24630?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D166= 41327#comment-16641327 ]=20 Jungtaek Lim commented on SPARK-24630: -------------------------------------- [~Jackey Lee] For DDL=C2=A0it would be better to participate discussion on Spark dev. mai= ling list which Ryan Blue is driving. For 'stream' keyword, I'm not sure how using the keyword 'stream' makes hug= e difference. It can be a kind of marker to verify at least one of sources = is stream as well as sink=C2=A0is stream, but while I guess this proposal i= s inspired by Streaming SQL in Flink or Calcite, even Flink they=C2=A0no lo= nger using=C2=A0keyword 'stream'. "STREAM" is not available in BNF-grammar = in here:=C2=A0[https://ci.apache.org/projects/flink/flink-docs-stable/dev/t= able/sql.html] Spark is on the same page, even without stream keyword, once Spark determin= es whether one of source(s) and sink are both stream, query will work=C2=A0= as structured streaming. =C2=A0 > SPIP: Support SQLStreaming in Spark > ----------------------------------- > > Key: SPARK-24630 > URL: https://issues.apache.org/jira/browse/SPARK-24630 > Project: Spark > Issue Type: Improvement > Components: Structured Streaming > Affects Versions: 2.2.0, 2.2.1 > Reporter: Jackey Lee > Priority: Minor > Labels: SQLStreaming > Attachments: SQLStreaming SPIP.pdf > > > At present, KafkaSQL, Flink SQL(which is actually based on Calcite), SQLS= tream, StormSQL all provide a stream type SQL interface, with which users w= ith little knowledge about streaming,=C2=A0 can easily develop a flow syste= m processing model. In Spark, we can also support SQL API based on StructSt= reamig. > To support for SQL Streaming, there are two key points:=C2=A0 > 1, Analysis should be able to parse streaming type SQL.=C2=A0 > 2, Analyzer should be able to map metadata information to the correspondi= ng=C2=A0 > Relation.=C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org For additional commands, e-mail: issues-help@spark.apache.org