[jira] [Resolved] (IGNITE-6518) Smarter analysis of INSERT and MERGE statements at parsing stage
[ https://issues.apache.org/jira/browse/IGNITE-6518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-6518. - Resolution: Won't Fix (was: Fixed) > Smarter analysis of INSERT and MERGE statements at parsing stage > > > Key: IGNITE-6518 > URL: https://issues.apache.org/jira/browse/IGNITE-6518 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Alexander Paschenko >Priority: Major > > We could analyze INSERT and MERGE statements to detect that they don't > specify data for key and/or value to notify users early that their query > can't be executed within Ignite - prior to building plans and attempting to > actually do anything. > (Note how we check that CREATE TABLE doesn't declare columns for key - logic > here would be similar.) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-6518) Smarter analysis of INSERT and MERGE statements at parsing stage
[ https://issues.apache.org/jira/browse/IGNITE-6518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-6518. - Resolution: Fixed Not relevant at the moment. Will be re-opened if needed. > Smarter analysis of INSERT and MERGE statements at parsing stage > > > Key: IGNITE-6518 > URL: https://issues.apache.org/jira/browse/IGNITE-6518 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Alexander Paschenko >Priority: Major > > We could analyze INSERT and MERGE statements to detect that they don't > specify data for key and/or value to notify users early that their query > can't be executed within Ignite - prior to building plans and attempting to > actually do anything. > (Note how we check that CREATE TABLE doesn't declare columns for key - logic > here would be similar.) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
