[JBoss JIRA] (TEIID-4405) delete using in statement does not remove records from temporary table
by Bram Gadeyne (JIRA)
Bram Gadeyne created TEIID-4405:
-----------------------------------
Summary: delete using in statement does not remove records from temporary table
Key: TEIID-4405
URL: https://issues.jboss.org/browse/TEIID-4405
Project: Teiid
Issue Type: Bug
Affects Versions: 9.0.2
Reporter: Bram Gadeyne
Assignee: Steven Hawkins
Priority: Critical
Hi,
I have a temporary table called #tmp_cohort that was constructed using this create statement.
create local temporary table #tmp_cohort(
patientid integer not null,
age float not null,
sex string not null,
patgroup string not null,
admtime timestamp not null,
distime timestamp not null,
los long not null,
icuoutcome string,
hospoutcome string,
PRIMARY KEY(patientid)
);
After filling it up it contains 12230 records. I only want to keep 10 records and remove the rest.
When I do the following select it does indeed return the 10 records I want to keep.
select *
from #tmp_cohort c
where c.patientid in (24123,55785,16667,53701,30763,59762,22679,46328,46453,55956)
The delete command however returns "0 rows deleted":
delete from #tmp_cohort
where patientid not in (24123,55785,16667,53701,30763,59762,22679,46328,46453,55956);
This is the query plan:
============================================================================
USER COMMAND:
DELETE FROM #tmp_cohort WHERE #tmp_cohort.patientid NOT IN (24123, 55785, 16667, 53701, 30763, 59762, 22679, 46328, 46453, 55956)
----------------------------------------------------------------------------
OPTIMIZE:
DELETE FROM #tmp_cohort WHERE #tmp_cohort.patientid NOT IN (24123, 55785, 16667, 53701, 30763, 59762, 22679, 46328, 46453, 55956)
----------------------------------------------------------------------------
GENERATE CANONICAL:
DELETE FROM #tmp_cohort WHERE #tmp_cohort.patientid NOT IN (24123, 55785, 16667, 53701, 30763, 59762, 22679, 46328, 46453, 55956)
CANONICAL PLAN:
Project(groups=[], props={PROJECT_COLS=[Count]})
Source(groups=[#tmp_cohort], props={ATOMIC_REQUEST=DELETE FROM #tmp_cohort WHERE #tmp_cohort.patientid NOT IN (24123, 55785, 16667, 53701, 30763, 59762, 22679, 46328, 46453, 55956), VIRTUAL_COMMAND=DELETE FROM #tmp_cohort WHERE #tmp_cohort.patientid NOT IN (24123, 55785, 16667, 53701, 30763, 59762, 22679, 46328, 46453, 55956)})
============================================================================
EXECUTING PlaceAccess
AFTER:
Project(groups=[], props={PROJECT_COLS=[Count]})
Access(groups=[#tmp_cohort], props={SOURCE_HINT=null, MODEL_ID=__TEMP__})
Source(groups=[#tmp_cohort], props={ATOMIC_REQUEST=DELETE FROM #tmp_cohort WHERE #tmp_cohort.patientid NOT IN (24123, 55785, 16667, 53701, 30763, 59762, 22679, 46328, 46453, 55956), VIRTUAL_COMMAND=DELETE FROM #tmp_cohort WHERE #tmp_cohort.patientid NOT IN (24123, 55785, 16667, 53701, 30763, 59762, 22679, 46328, 46453, 55956)})
============================================================================
EXECUTING RaiseAccess
AFTER:
Access(groups=[#tmp_cohort], props={SOURCE_HINT=null, MODEL_ID=__TEMP__})
Project(groups=[], props={PROJECT_COLS=[Count]})
Source(groups=[#tmp_cohort], props={ATOMIC_REQUEST=DELETE FROM #tmp_cohort WHERE #tmp_cohort.patientid NOT IN (24123, 55785, 16667, 53701, 30763, 59762, 22679, 46328, 46453, 55956), VIRTUAL_COMMAND=DELETE FROM #tmp_cohort WHERE #tmp_cohort.patientid NOT IN (24123, 55785, 16667, 53701, 30763, 59762, 22679, 46328, 46453, 55956)})
============================================================================
EXECUTING AssignOutputElements
AFTER:
Access(groups=[#tmp_cohort], props={SOURCE_HINT=null, MODEL_ID=__TEMP__, OUTPUT_COLS=[Count]})
Project(groups=[], props={PROJECT_COLS=[Count], OUTPUT_COLS=[Count]})
Source(groups=[#tmp_cohort], props={ATOMIC_REQUEST=DELETE FROM #tmp_cohort WHERE #tmp_cohort.patientid NOT IN (24123, 55785, 16667, 53701, 30763, 59762, 22679, 46328, 46453, 55956), VIRTUAL_COMMAND=DELETE FROM #tmp_cohort WHERE #tmp_cohort.patientid NOT IN (24123, 55785, 16667, 53701, 30763, 59762, 22679, 46328, 46453, 55956), OUTPUT_COLS=[Count]})
============================================================================
EXECUTING CalculateCost
AFTER:
Access(groups=[#tmp_cohort], props={SOURCE_HINT=null, MODEL_ID=__TEMP__, OUTPUT_COLS=[Count], EST_CARDINALITY=12230.0, EST_COL_STATS={Count=[-1.0, -1.0]}})
Project(groups=[], props={PROJECT_COLS=[Count], OUTPUT_COLS=[Count], EST_CARDINALITY=12230.0, EST_COL_STATS={Count=[-1.0, -1.0]}})
Source(groups=[#tmp_cohort], props={ATOMIC_REQUEST=DELETE FROM #tmp_cohort WHERE #tmp_cohort.patientid NOT IN (24123, 55785, 16667, 53701, 30763, 59762, 22679, 46328, 46453, 55956), VIRTUAL_COMMAND=DELETE FROM #tmp_cohort WHERE #tmp_cohort.patientid NOT IN (24123, 55785, 16667, 53701, 30763, 59762, 22679, 46328, 46453, 55956), OUTPUT_COLS=[Count], EST_CARDINALITY=12230.0})
============================================================================
EXECUTING PlanSorts
AFTER:
Access(groups=[#tmp_cohort])
Project(groups=[])
Source(groups=[#tmp_cohort])
============================================================================
EXECUTING CollapseSource
AFTER:
Access(groups=[#tmp_cohort], props={SOURCE_HINT=null, MODEL_ID=__TEMP__, OUTPUT_COLS=[Count], EST_CARDINALITY=12230.0, EST_COL_STATS={Count=[-1.0, -1.0]}, ATOMIC_REQUEST=DELETE FROM #tmp_cohort WHERE #tmp_cohort.patientid NOT IN (24123, 55785, 16667, 53701, 30763, 59762, 22679, 46328, 46453, 55956)})
============================================================================
CONVERTING PLAN TREE TO PROCESS TREE
PROCESS PLAN =
AccessNode(0) output=[Count] DELETE FROM #tmp_cohort WHERE #tmp_cohort.patientid NOT IN (24123, 55785, 16667, 53701, 30763, 59762, 22679, 46328, 46453, 55956)
============================================================================
----------------------------------------------------------------------------
OPTIMIZATION COMPLETE:
PROCESSOR PLAN:
AccessNode(0) output=[Count] DELETE FROM #tmp_cohort WHERE #tmp_cohort.patientid NOT IN (24123, 55785, 16667, 53701, 30763, 59762, 22679, 46328, 46453, 55956)
============================================================================
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4404) Install CLI should pre-run before dist build
by Kylin Soong (JIRA)
Kylin Soong created TEIID-4404:
----------------------------------
Summary: Install CLI should pre-run before dist build
Key: TEIID-4404
URL: https://issues.jboss.org/browse/TEIID-4404
Project: Teiid
Issue Type: Feature Request
Affects Versions: 9.1
Reporter: Kylin Soong
Assignee: Steven Hawkins
In teiid we have provide a server dist(http://teiid.jboss.org/downloads/, With WildFly), but it not install teiid in advanced, after download the dist, we have to execute
{code}
./bin/standalone.sh
./bin/jboss-cli.sh --connect --file=bin/scripts/teiid-standalone-mode-install.cli
./bin/domain.sh
./bin/jboss-cli.sh --connect --file=bin/scripts/teiid-domain-mode-install.cli
./bin/add-user.sh -a -u dashboardAdmin -p password1! -g admin
./bin/add-user.sh -a -u teiidUser -p password1! -g user
./bin/add-user.sh -a -u restUser -p password1! -g rest
./bin/add-user.sh -a -u odataUser -p password1! -g odata
./bin/add-user.sh admin password1!
{code}
However, in other JBoss product, like infinispan(http://infinispan.org/download/), jbpm, the server dist, download can run directly, do not need run any install cli.
So, I do wonder if we can do some adjustment that make teiid compatible with other jboss product.
In addition, as [1], configure api depend on a server dist which can run directly, now, it have to start teiid server manually.
[1] https://github.com/teiid/wildfly-swarm-teiid/tree/master/config-api
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-3825) Add a wildfly-swarm-teiid Fraction for running teiid as an uberjar
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-3825?page=com.atlassian.jira.plugin... ]
Kylin Soong commented on TEIID-3825:
------------------------------------
Kylin—
We have started to attempt to perform a release on the first Monday of each month. If you’d like to plan your schedule around that for your releases, that would probably work. We may not release some months, though.
Additionally, I’d recommend the following:
a) Produce your feature-pack as part of the core Teiid build. Keycloak, Hawkular and others follow this process, and it ensures that your feature-pack stays aligned with your upstream project. Additionally, it can be consumed by the wildfly-server-provisioning-plugin when you create your standalone normal WildFly-based distribution.
b) I’d probably adjust your config-api build to no check sources into your repository, but rather just produce your .jar and publish to a maven repository. I understand our config-api generator may not be very easy to use for 3rd parties at the moment, and we’ll definitely work with you to make it work better for your situation.
We hang out in #wildfly-swarm on FreeNode IRC if you need any other advice or assistance.
-Bob
> Add a wildfly-swarm-teiid Fraction for running teiid as an uberjar
> ------------------------------------------------------------------
>
> Key: TEIID-3825
> URL: https://issues.jboss.org/browse/TEIID-3825
> Project: Teiid
> Issue Type: Feature Request
> Components: Embedded
> Affects Versions: 9.0
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 9.x
>
>
> Fractions within WildFly Swarm are roughly equivalent to subsystems within WildFly, we have teiid subsystem in Server mode, so I think a Fraction is necessary to run teiid with Swarm.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4393) Add new Geospatial functions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4393?page=com.atlassian.jira.plugin... ]
Steven Hawkins edited comment on TEIID-4393 at 8/22/16 8:11 PM:
----------------------------------------------------------------
The total function list to be added is:
ST_AREA
ST_BOUNDARY
ST_BUFFER
ST_CENTROID
ST_CONVEXHULL
ST_COORDDIM
ST_CURVETOLINE
ST_DIFFERENCE
ST_DIMENSION
ST_ENDPOINT
ST_EXTERIORRING
ST_GEOMETRYN
ST_GEOMETRYTYPE
ST_INTERIORRINGN
ST_ISCLOSED
ST_ISEMPTY
ST_ISRING
ST_ISSIMPLE
ST_ISVALID
ST_LENGTH
ST_NUMGEOMETRIES
ST_NUMINTERIORRINGS
ST_NUMPOINTS
ST_ORDERINGEQUALS
ST_PERIMETER
ST_POINT
ST_POINTN
ST_POINTONSURFACE
ST_POLYGON
ST_RELATE
ST_STARTPOINT
ST_SYMDIFFERENCE
ST_UNION
ST_X
ST_Y
ST_Z
ST_PATCHN and ST_NUMPATCHES will not be added at this time. From what I see with postgis, these just act as aliases to ST_GEOMETRYN and ST_NUMGEOMETRIES, and we weren't able to provide real implementations.
was (Author: shawkins):
The total function list to be added is:
ST_AREA
ST_BOUNDARY
ST_BUFFER
ST_CENTROID
ST_CONVEXHULL
ST_COORDDIM
ST_CURVETOLINE
ST_DIFFERENCE
ST_DIMENSION
ST_ENDPOINT
ST_EXTERIORRING
ST_GEOMETRYN
ST_GEOMETRYTYPE
ST_INTERIORRINGN
ST_ISCLOSED
ST_ISEMPTY
ST_ISRING
ST_ISSIMPLE
ST_ISVALID
ST_LENGTH
ST_NUMGEOMETRIES
ST_NUMINTERIORRINGS
ST_NUMPATCHES
ST_NUMPOINTS
ST_ORDERINGEQUALS
ST_PATCHN
ST_PERIMETER
ST_POINT
ST_POINTN
ST_POINTONSURFACE
ST_POLYGON
ST_RELATE
ST_STARTPOINT
ST_SYMDIFFERENCE
ST_UNION
ST_X
ST_Y
ST_Z
> Add new Geospatial functions
> ----------------------------
>
> Key: TEIID-4393
> URL: https://issues.jboss.org/browse/TEIID-4393
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.12.x, 9.x
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 9.1
>
>
> Adding a list of geospatial features to be added. Used the following specification: https://portal.opengeospatial.org/files/?artifact_id=829
> st_Dimension
> st_GeometryType
> st_IsEmpty
> st_IsSimple
> st_Boundary
> st_Envelope
> st_X
> st_Y
> st_StartPoint
> st_EndPoint
> st_Boundary
> st_Boundary
> st_Length
> st_NumPoints
> st_PointN
> st_Centroid
> st_PointOnSurface
> st_Area
> st_ExteriorRing
> st_NumInteriorRings
> st_InteriorRingN
> st_NumGeometries
> st_GeometryN
> st_IsClosed
> st_Length
> st_Centroid
> st_PointOnSurface
> st_Area
> st_Within
> st_Relate
> st_Intersection
> st_Difference
> st_Union
> st_SymmetricDifference
> st_Buffer
> st_ConvexHull
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4393) Add new Geospatial functions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4393?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4393:
---------------------------------------
The total function list to be added is:
ST_AREA
ST_BOUNDARY
ST_BUFFER
ST_CENTROID
ST_CONVEXHULL
ST_COORDDIM
ST_CURVETOLINE
ST_DIFFERENCE
ST_DIMENSION
ST_ENDPOINT
ST_EXTERIORRING
ST_GEOMETRYN
ST_GEOMETRYTYPE
ST_INTERIORRINGN
ST_ISCLOSED
ST_ISEMPTY
ST_ISRING
ST_ISSIMPLE
ST_ISVALID
ST_LENGTH
ST_NUMGEOMETRIES
ST_NUMINTERIORRINGS
ST_NUMPATCHES
ST_NUMPOINTS
ST_ORDERINGEQUALS
ST_PATCHN
ST_PERIMETER
ST_POINT
ST_POINTN
ST_POINTONSURFACE
ST_POLYGON
ST_RELATE
ST_STARTPOINT
ST_SYMDIFFERENCE
ST_UNION
ST_X
ST_Y
ST_Z
> Add new Geospatial functions
> ----------------------------
>
> Key: TEIID-4393
> URL: https://issues.jboss.org/browse/TEIID-4393
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.12.x, 9.x
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 9.1
>
>
> Adding a list of geospatial features to be added. Used the following specification: https://portal.opengeospatial.org/files/?artifact_id=829
> st_Dimension
> st_GeometryType
> st_IsEmpty
> st_IsSimple
> st_Boundary
> st_Envelope
> st_X
> st_Y
> st_StartPoint
> st_EndPoint
> st_Boundary
> st_Boundary
> st_Length
> st_NumPoints
> st_PointN
> st_Centroid
> st_PointOnSurface
> st_Area
> st_ExteriorRing
> st_NumInteriorRings
> st_InteriorRingN
> st_NumGeometries
> st_GeometryN
> st_IsClosed
> st_Length
> st_Centroid
> st_PointOnSurface
> st_Area
> st_Within
> st_Relate
> st_Intersection
> st_Difference
> st_Union
> st_SymmetricDifference
> st_Buffer
> st_ConvexHull
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4393) Add new Geospatial functions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4393?page=com.atlassian.jira.plugin... ]
Steven Hawkins edited comment on TEIID-4393 at 8/22/16 3:20 PM:
----------------------------------------------------------------
We can't directly implement curved geometry functions:
st_CurveToLine - we'll add so that it can be pushed
st_NumPatches - will always return null
st_PatchN - will always return null
I mis-read the others, which are polygon functions, so those can still added.
was (Author: shawkins):
We can't directly implement curved geometry functions:
st_CurveToLine - we'll add so that it can be pushed
st_NumPatches - will always return null
I mis-read the others, which are polygon functions, so those can still added.
> Add new Geospatial functions
> ----------------------------
>
> Key: TEIID-4393
> URL: https://issues.jboss.org/browse/TEIID-4393
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.12.x, 9.x
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 9.1
>
>
> Adding a list of geospatial features to be added. Used the following specification: https://portal.opengeospatial.org/files/?artifact_id=829
> st_Dimension
> st_GeometryType
> st_IsEmpty
> st_IsSimple
> st_Boundary
> st_Envelope
> st_X
> st_Y
> st_StartPoint
> st_EndPoint
> st_Boundary
> st_Boundary
> st_Length
> st_NumPoints
> st_PointN
> st_Centroid
> st_PointOnSurface
> st_Area
> st_ExteriorRing
> st_NumInteriorRings
> st_InteriorRingN
> st_NumGeometries
> st_GeometryN
> st_IsClosed
> st_Length
> st_Centroid
> st_PointOnSurface
> st_Area
> st_Within
> st_Relate
> st_Intersection
> st_Difference
> st_Union
> st_SymmetricDifference
> st_Buffer
> st_ConvexHull
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-3836) Create a quick start to demonstrate OData
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3836?page=com.atlassian.jira.plugin... ]
Van Halbert edited comment on TEIID-3836 at 8/22/16 2:46 PM:
-------------------------------------------------------------
By adding Primary Key's to the views, was able to use Odata.
was (Author: van.halbert):
By adding Primary Key's to the views, was able to use Odata. I'll update the quickstart README.
> Create a quick start to demonstrate OData
> -----------------------------------------
>
> Key: TEIID-3836
> URL: https://issues.jboss.org/browse/TEIID-3836
> Project: Teiid
> Issue Type: Task
> Components: Quick Starts
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Van Halbert
> Fix For: 9.1
>
>
> Add a quick start to demonstrate OData api may helpful for users.
> After deploy portfolio-vdb.xml successful, I test with(http://localhost:8080/odata/Portfolio.1/Stocks.StockPrices) return a error:
> {code}
> TEIID16011 EntitySet "Stocks.StockPrices" is not found; Check the spelling, use modelName.tableName; The table that representing the Entity type must either have a PRIMARY KEY or UNIQUE key(s)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-3836) Create a quick start to demonstrate OData
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3836?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-3836:
------------------------------------
By adding Primary Key's to the views, was able to use Odata. I'll update the quickstart README.
> Create a quick start to demonstrate OData
> -----------------------------------------
>
> Key: TEIID-3836
> URL: https://issues.jboss.org/browse/TEIID-3836
> Project: Teiid
> Issue Type: Task
> Components: Quick Starts
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Van Halbert
> Fix For: 9.1
>
>
> Add a quick start to demonstrate OData api may helpful for users.
> After deploy portfolio-vdb.xml successful, I test with(http://localhost:8080/odata/Portfolio.1/Stocks.StockPrices) return a error:
> {code}
> TEIID16011 EntitySet "Stocks.StockPrices" is not found; Check the spelling, use modelName.tableName; The table that representing the Entity type must either have a PRIMARY KEY or UNIQUE key(s)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4393) Add new Geospatial functions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4393?page=com.atlassian.jira.plugin... ]
Steven Hawkins edited comment on TEIID-4393 at 8/22/16 12:55 PM:
-----------------------------------------------------------------
We can't directly implement curved geometry functions:
st_CurveToLine - we'll add so that it can be pushed
st_NumPatches - will always return null
I mis-read the others, which are polygon functions, so those can still added.
was (Author: shawkins):
We can't directly implement curved geometry functions:
st_CurveToLine - we'll add so that it can be pushed
st_NumInteriorRings - will always return null
Won't add:
st_ExteriorRing
st_InteriorRingN
> Add new Geospatial functions
> ----------------------------
>
> Key: TEIID-4393
> URL: https://issues.jboss.org/browse/TEIID-4393
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.12.x, 9.x
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 9.1
>
>
> Adding a list of geospatial features to be added. Used the following specification: https://portal.opengeospatial.org/files/?artifact_id=829
> st_Dimension
> st_GeometryType
> st_IsEmpty
> st_IsSimple
> st_Boundary
> st_Envelope
> st_X
> st_Y
> st_StartPoint
> st_EndPoint
> st_Boundary
> st_Boundary
> st_Length
> st_NumPoints
> st_PointN
> st_Centroid
> st_PointOnSurface
> st_Area
> st_ExteriorRing
> st_NumInteriorRings
> st_InteriorRingN
> st_NumGeometries
> st_GeometryN
> st_IsClosed
> st_Length
> st_Centroid
> st_PointOnSurface
> st_Area
> st_Within
> st_Relate
> st_Intersection
> st_Difference
> st_Union
> st_SymmetricDifference
> st_Buffer
> st_ConvexHull
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months