You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@metamodel.apache.org by "Jack Mueller (Jira)" <ji...@apache.org> on 2020/04/01 14:57:00 UTC

[jira] [Commented] (METAMODEL-1225) CSV Dataset cannot be filtered with numerical operations using a SQL string query

    [ https://issues.apache.org/jira/browse/METAMODEL-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072841#comment-17072841 ] 

Jack Mueller commented on METAMODEL-1225:
-----------------------------------------

I'm starting to look at this. Something similar to _ColumnNamingStrategy_ would be _ColumnTypingStrategy_ yes? Should it go in its own package org.apache.metamodel.schema.typing or should I try to combine it with the naming strategies so that we have _ColumnConfigurationStrategy_ that can have naming strategy, typing strategy, and whatever other configuration may be needed. If there is no other possible configuration maybe it's not necessary to combine them, but if they are combined we can reuse things like _ColumnNamingSession_ and _ColumnNamingContext_.

> CSV Dataset cannot be filtered with numerical operations using a SQL string query
> ---------------------------------------------------------------------------------
>
>                 Key: METAMODEL-1225
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-1225
>             Project: Apache MetaModel
>          Issue Type: Bug
>            Reporter: Jack Mueller
>            Priority: Major
>
> When querying a CSV file with something of the form dataContext.execute("SELECT column1 FROM default_table WHERE column1 < 9"), Incorrect rows may be returned such as those where column2 = 11.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)