[jira] [Updated] (SPARK-17254) Filter operator should have “stop if false” semantics for sorted data
[ https://issues.apache.org/jira/browse/SPARK-17254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hyukjin Kwon updated SPARK-17254: - Labels: bulk-closed (was: ) > Filter operator should have “stop if false” semantics for sorted data > - > > Key: SPARK-17254 > URL: https://issues.apache.org/jira/browse/SPARK-17254 > Project: Spark > Issue Type: Sub-task > Components: SQL >Reporter: Tejas Patil >Priority: Major > Labels: bulk-closed > Attachments: stop-after-physical-plan.pdf > > > From > https://issues.apache.org/jira/secure/attachment/12778890/BucketedTables.pdf: > Filter on sorted data > If the data is sorted by a key, filters on the key could stop as soon as the > data is out of range. For example, WHERE ticker_id < “F” should stop as soon > as the first row starting with “F” is seen. This can be done adding a Filter > operator that has “stop if false” semantics. This is generally useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-17254) Filter operator should have “stop if false” semantics for sorted data
[ https://issues.apache.org/jira/browse/SPARK-17254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynold Xin updated SPARK-17254: Issue Type: Sub-task (was: Improvement) Parent: SPARK-18245 > Filter operator should have “stop if false” semantics for sorted data > - > > Key: SPARK-17254 > URL: https://issues.apache.org/jira/browse/SPARK-17254 > Project: Spark > Issue Type: Sub-task > Components: SQL >Reporter: Tejas Patil > Attachments: stop-after-physical-plan.pdf > > > From > https://issues.apache.org/jira/secure/attachment/12778890/BucketedTables.pdf: > Filter on sorted data > If the data is sorted by a key, filters on the key could stop as soon as the > data is out of range. For example, WHERE ticker_id < “F” should stop as soon > as the first row starting with “F” is seen. This can be done adding a Filter > operator that has “stop if false” semantics. This is generally useful. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-17254) Filter operator should have “stop if false” semantics for sorted data
[ https://issues.apache.org/jira/browse/SPARK-17254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liang-Chi Hsieh updated SPARK-17254: Attachment: (was: stop-after-physical-plan.pdf) > Filter operator should have “stop if false” semantics for sorted data > - > > Key: SPARK-17254 > URL: https://issues.apache.org/jira/browse/SPARK-17254 > Project: Spark > Issue Type: Improvement > Components: SQL >Reporter: Tejas Patil > Attachments: stop-after-physical-plan.pdf > > > From > https://issues.apache.org/jira/secure/attachment/12778890/BucketedTables.pdf: > Filter on sorted data > If the data is sorted by a key, filters on the key could stop as soon as the > data is out of range. For example, WHERE ticker_id < “F” should stop as soon > as the first row starting with “F” is seen. This can be done adding a Filter > operator that has “stop if false” semantics. This is generally useful. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-17254) Filter operator should have “stop if false” semantics for sorted data
[ https://issues.apache.org/jira/browse/SPARK-17254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liang-Chi Hsieh updated SPARK-17254: Attachment: stop-after-physical-plan.pdf > Filter operator should have “stop if false” semantics for sorted data > - > > Key: SPARK-17254 > URL: https://issues.apache.org/jira/browse/SPARK-17254 > Project: Spark > Issue Type: Improvement > Components: SQL >Reporter: Tejas Patil > Attachments: stop-after-physical-plan.pdf > > > From > https://issues.apache.org/jira/secure/attachment/12778890/BucketedTables.pdf: > Filter on sorted data > If the data is sorted by a key, filters on the key could stop as soon as the > data is out of range. For example, WHERE ticker_id < “F” should stop as soon > as the first row starting with “F” is seen. This can be done adding a Filter > operator that has “stop if false” semantics. This is generally useful. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-17254) Filter operator should have “stop if false” semantics for sorted data
[ https://issues.apache.org/jira/browse/SPARK-17254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liang-Chi Hsieh updated SPARK-17254: Attachment: (was: stop-after-physical-plan.pdf) > Filter operator should have “stop if false” semantics for sorted data > - > > Key: SPARK-17254 > URL: https://issues.apache.org/jira/browse/SPARK-17254 > Project: Spark > Issue Type: Improvement > Components: SQL >Reporter: Tejas Patil > Attachments: stop-after-physical-plan.pdf > > > From > https://issues.apache.org/jira/secure/attachment/12778890/BucketedTables.pdf: > Filter on sorted data > If the data is sorted by a key, filters on the key could stop as soon as the > data is out of range. For example, WHERE ticker_id < “F” should stop as soon > as the first row starting with “F” is seen. This can be done adding a Filter > operator that has “stop if false” semantics. This is generally useful. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-17254) Filter operator should have “stop if false” semantics for sorted data
[ https://issues.apache.org/jira/browse/SPARK-17254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liang-Chi Hsieh updated SPARK-17254: Attachment: stop-after-physical-plan.pdf > Filter operator should have “stop if false” semantics for sorted data > - > > Key: SPARK-17254 > URL: https://issues.apache.org/jira/browse/SPARK-17254 > Project: Spark > Issue Type: Improvement > Components: SQL >Reporter: Tejas Patil > Attachments: stop-after-physical-plan.pdf > > > From > https://issues.apache.org/jira/secure/attachment/12778890/BucketedTables.pdf: > Filter on sorted data > If the data is sorted by a key, filters on the key could stop as soon as the > data is out of range. For example, WHERE ticker_id < “F” should stop as soon > as the first row starting with “F” is seen. This can be done adding a Filter > operator that has “stop if false” semantics. This is generally useful. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-17254) Filter operator should have “stop if false” semantics for sorted data
[ https://issues.apache.org/jira/browse/SPARK-17254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liang-Chi Hsieh updated SPARK-17254: Priority: Major (was: Minor) > Filter operator should have “stop if false” semantics for sorted data > - > > Key: SPARK-17254 > URL: https://issues.apache.org/jira/browse/SPARK-17254 > Project: Spark > Issue Type: Improvement > Components: SQL >Reporter: Tejas Patil > Attachments: stop-after-physical-plan.pdf > > > From > https://issues.apache.org/jira/secure/attachment/12778890/BucketedTables.pdf: > Filter on sorted data > If the data is sorted by a key, filters on the key could stop as soon as the > data is out of range. For example, WHERE ticker_id < “F” should stop as soon > as the first row starting with “F” is seen. This can be done adding a Filter > operator that has “stop if false” semantics. This is generally useful. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-17254) Filter operator should have “stop if false” semantics for sorted data
[ https://issues.apache.org/jira/browse/SPARK-17254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liang-Chi Hsieh updated SPARK-17254: Attachment: stop-after-physical-plan.pdf > Filter operator should have “stop if false” semantics for sorted data > - > > Key: SPARK-17254 > URL: https://issues.apache.org/jira/browse/SPARK-17254 > Project: Spark > Issue Type: Improvement > Components: SQL >Reporter: Tejas Patil >Priority: Minor > Attachments: stop-after-physical-plan.pdf > > > From > https://issues.apache.org/jira/secure/attachment/12778890/BucketedTables.pdf: > Filter on sorted data > If the data is sorted by a key, filters on the key could stop as soon as the > data is out of range. For example, WHERE ticker_id < “F” should stop as soon > as the first row starting with “F” is seen. This can be done adding a Filter > operator that has “stop if false” semantics. This is generally useful. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
