May 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5753) Please add extension metadata support to allow for an invisibility option on single foreign tables/views for odata layer

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5753?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5753: ---------------------------------- Fix Version/s: 13.0 > Please add extension metadata support to allow for an invisibility option on single foreign tables/views for odata layer > ------------------------------------------------------------------------------------------------------------------------ > > Key: TEIID-5753 > URL: https://issues.jboss.org/browse/TEIID-5753 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > The issue arose from the discussion at > https://developer.jboss.org/message/989502#989502 > > Every tables and view I specify is becoming visible in the odata service. Of course I can use GRANT to resctrict access, however, it would be more nice to not export the tables in the odata layer in the first place. Would it be possible to add some kind of per table/view INVISIBLE OPTION for odata, or could I reach the same result in a different way and how would this look like? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5756) null session query output from PDI

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5756?page=com.atlassian.jira.plugin... ] Steven Hawkins moved TEIIDTOOLS-566 to TEIID-5756: -------------------------------------------------- Project: Teiid (was: Teiid Tools) Key: TEIID-5756 (was: TEIIDTOOLS-566) Component/s: Server (was: data-sources) (was: vdb-bench) > null session query output from PDI > ---------------------------------- > > Key: TEIID-5756 > URL: https://issues.jboss.org/browse/TEIID-5756 > Project: Teiid > Issue Type: Bug > Components: Server > Environment: Prod > Reporter: CHANDAN BISHT > Priority: Major > Attachments: jdvapp1.tar.gz, jdvapp3.tar.gz, server.log.1 > > > User getting null session query executed from PDI tool. > the session id tvgWrPf4oPvD > 2019-02-04 09:21:42,987 [New I/O worker #39] WARN [org.teiid.PROCESSOR] TEIID40011 Processing exception 'TEIID40042 Invalid Session tvgWrPf4oPvD. Session may have already been terminated.' for session null. Exception type org.teiid.client.security.InvalidSessionException thrown from org.teiid.jboss.TransportService$2.invoke(TransportService.java:239).: org.teiid.client.security.InvalidSessionException: TEIID40042 Invalid Session tvgWrPf4oPvD. Session may have already been terminated. > at org.teiid.jboss.TransportService$2.invoke(TransportService.java:239) > at com.sun.proxy.$Proxy20.processCursorRequest(Unknown Source) > at sun.reflect.GeneratedMethodAccessor152.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.teiid.transport.ServerWorkItem.run(ServerWorkItem.java:87) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284) > at org.teiid.transport.SocketClientInstance.processMessagePacket(SocketClientInstance.java:231) > at org.teiid.transport.SocketClientInstance.receivedMessage(SocketClientInstance.java:217) > at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:216) > at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88) > at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) > at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:142) > at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) > at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-100) move static handling to the root context

by Steven Hawkins (Jira)

Steven Hawkins created TEIIDSB-100: -------------------------------------- Summary: move static handling to the root context Key: TEIIDSB-100 URL: https://issues.jboss.org/browse/TEIIDSB-100 Project: Teiid Spring Boot Issue Type: Quality Risk Components: OData Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 1.2.0 To prevent conflicts with entity and schema names, static handling should be moved to the root level: /odata/... /static/... rather than /odata/static It's also a good idea to fully restrict the resources that can be read as all xml files in the unified classpath are currently accessible. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-99) actuator endpoint secured incorrectly

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-99?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIIDSB-99. ----------------------------------- Resolution: Done Corrected the context for the health check. > actuator endpoint secured incorrectly > ------------------------------------- > > Key: TEIIDSB-99 > URL: https://issues.jboss.org/browse/TEIIDSB-99 > Project: Teiid Spring Boot > Issue Type: Bug > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.2.0, 7.4-1.1.1 > > > Over a couple of refactorings the odata prefix was mistakenly added to the actuator health check endpoint in the SecurityConfig. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-99) actuator endpoint secured incorrectly

by Steven Hawkins (Jira)

Steven Hawkins created TEIIDSB-99: ------------------------------------- Summary: actuator endpoint secured incorrectly Key: TEIIDSB-99 URL: https://issues.jboss.org/browse/TEIIDSB-99 Project: Teiid Spring Boot Issue Type: Bug Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 1.1.1, 1.2.0 Over a couple of refactorings the odata prefix was mistakenly added to the actuator health check endpoint in the SecurityConfig. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-98) Expose openapi.json instead of or in addition to swagger.json

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-98?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIIDSB-98. ----------------------------------- Resolution: Duplicate Issue Duplicate of TEIIDSB-62 > Expose openapi.json instead of or in addition to swagger.json > ------------------------------------------------------------- > > Key: TEIIDSB-98 > URL: https://issues.jboss.org/browse/TEIIDSB-98 > Project: Teiid Spring Boot > Issue Type: Task > Components: OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > > expose the OData OpenAPI metadata document at openapi.json in addition to swagger.json -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-98) Expose openapi.json instead of or in addition to swagger.json

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-98: ----------------------------------- Summary: Expose openapi.json instead of or in addition to swagger.json Key: TEIIDSB-98 URL: https://issues.jboss.org/browse/TEIIDSB-98 Project: Teiid Spring Boot Issue Type: Task Components: OData Reporter: Ramesh Reddy Assignee: Ramesh Reddy expose the OData OpenAPI metadata document at openapi.json in addition to swagger.json -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5755) Clarify import foreign schema

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5755?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5755. ----------------------------------- Resolution: Done Changed the parse so that the FOREIGN SCHEMA name is optional. For ddl you can just do: IMPORT FROM REPOSITORY... Updated the docs accordingly and expanded the example to show importing from multiple files. > Clarify import foreign schema > ----------------------------- > > Key: TEIID-5755 > URL: https://issues.jboss.org/browse/TEIID-5755 > Project: Teiid > Issue Type: Quality Risk > Components: Documentation, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > Since we don't have some kind of evaluate directive for ddl, we use the import foreign schema construct in a similar manner by using the ddl-file repository type. > It's possible to split ddl for a schema into multiple file, which should be described in the docs. > It's also possible to use import foreign schema into a virtual schema, but the foreign keyword is still required. It should be made optional and described as ignored in the docs. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5755) Clarify import foreign schema

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5755: ------------------------------------- Summary: Clarify import foreign schema Key: TEIID-5755 URL: https://issues.jboss.org/browse/TEIID-5755 Project: Teiid Issue Type: Quality Risk Components: Documentation, Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.3 Since we don't have some kind of evaluate directive for ddl, we use the import foreign schema construct in a similar manner by using the ddl-file repository type. It's possible to split ddl for a schema into multiple file, which should be described in the docs. It's also possible to use import foreign schema into a virtual schema, but the foreign keyword is still required. It should be made optional and described as ignored in the docs. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5481) Evaluate JSONPATH as expression language for Json payload to table

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5481?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5481: --------------------------------------- I'll update the pr with at least parsing support for the jsontable syntax, then look to merge into 12.3. > Evaluate JSONPATH as expression language for Json payload to table > ------------------------------------------------------------------ > > Key: TEIID-5481 > URL: https://issues.jboss.org/browse/TEIID-5481 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > Currently in Teiid in order to turn a JSON document to a relational structure, JSONTOXML function is used then XPATH used on it to retrieve data using XMLTABLE. > Investigate the feasibility of using JSONPATH [1] directly on JSON document to build a JSONTABLE construct. > [1] https://code.google.com/archive/p/json-path/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2019