[JBoss JIRA] (TEIID-4908) Access Pattern Messaging
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIID-4908?page=com.atlassian.jira.plugin... ]
Steve Tran closed TEIID-4908.
-----------------------------
Resolution: Won't Do
Nevermind, the friendly names are there, just a little hidden.
> Access Pattern Messaging
> ------------------------
>
> Key: TEIID-4908
> URL: https://issues.jboss.org/browse/TEIID-4908
> Project: Teiid
> Issue Type: Feature Request
> Affects Versions: 8.12.8.6_3
> Environment: JDV 6.3.2
> Windows 7
> Reporter: Steve Tran
> Assignee: Steven Hawkins
>
> When accessing a table that has an Access Pattern defined, the columns defined in the access pattern don't necessarily match the columns being exposed by the view.
> I'm aliasing the output of the query with friendly column names, while the Access Pattern defines the access based on the real column names. When the user sees the Access Pattern warning message, it can be confusing as to what columns they actually need to supply.
> Here's a real error message. In my view, I didn't define any of my columns with an underscore, I camel-cased everything.
> {code}
> <error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
> <code>TEIID30278</code>
> <message>
> TEIID30278 Group has an access pattern which has not been met: group(s) [TDSA.V_RPT_T_MER_ADDN]; access pattern(s) [Access Pattern: Unsatisfied [TDSA.V_RPT_T_MER_ADDN.MID_TAG] History [[TDSA.V_RPT_T_MER_ADDN.MID_TAG], [MID_TAG], [g0.midTag]], Access Pattern: Unsatisfied [TDSA.V_RPT_T_MER_ADDN.MID_GROUP] History [[TDSA.V_RPT_T_MER_ADDN.EXTERNAL_MID, TDSA.V_RPT_T_MER_ADDN.MID_GROUP], [MID_GROUP, EXTERNAL_MID], [g0.midGroup, g0.mid]]]
> </message>
> </error>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4908) Access Pattern Messaging
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIID-4908?page=com.atlassian.jira.plugin... ]
Steve Tran updated TEIID-4908:
------------------------------
Issue Type: Enhancement (was: Bug)
> Access Pattern Messaging
> ------------------------
>
> Key: TEIID-4908
> URL: https://issues.jboss.org/browse/TEIID-4908
> Project: Teiid
> Issue Type: Enhancement
> Affects Versions: 8.12.8.6_3
> Environment: JDV 6.3.2
> Windows 7
> Reporter: Steve Tran
> Assignee: Steven Hawkins
>
> When accessing a table that has an Access Pattern defined, the columns defined in the access pattern don't necessarily match the columns being exposed by the view.
> I'm aliasing the output of the query with friendly column names, while the Access Pattern defines the access based on the real column names. When the user sees the Access Pattern warning message, it can be confusing as to what columns they actually need to supply.
> Here's a real error message. In my view, I didn't define any of my columns with an underscore, I camel-cased everything.
> {code}
> <error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
> <code>TEIID30278</code>
> <message>
> TEIID30278 Group has an access pattern which has not been met: group(s) [TDSA.V_RPT_T_MER_ADDN]; access pattern(s) [Access Pattern: Unsatisfied [TDSA.V_RPT_T_MER_ADDN.MID_TAG] History [[TDSA.V_RPT_T_MER_ADDN.MID_TAG], [MID_TAG], [g0.midTag]], Access Pattern: Unsatisfied [TDSA.V_RPT_T_MER_ADDN.MID_GROUP] History [[TDSA.V_RPT_T_MER_ADDN.EXTERNAL_MID, TDSA.V_RPT_T_MER_ADDN.MID_GROUP], [MID_GROUP, EXTERNAL_MID], [g0.midGroup, g0.mid]]]
> </message>
> </error>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4908) Access Pattern Messaging
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIID-4908?page=com.atlassian.jira.plugin... ]
Steve Tran updated TEIID-4908:
------------------------------
Description:
When accessing a table that has an Access Pattern defined, the columns defined in the access pattern don't necessarily match the columns being exposed by the view.
I'm aliasing the output of the query with friendly column names, while the Access Pattern defines the access based on the real column names. When the user sees the Access Pattern warning message, it can be confusing as to what columns they actually need to supply.
Here's a real error message. In my view, I didn't define any of my columns with an underscore, I camel-cased everything.
{code}
<error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
<code>TEIID30278</code>
<message>
TEIID30278 Group has an access pattern which has not been met: group(s) [TDSA.V_RPT_T_MER_ADDN]; access pattern(s) [Access Pattern: Unsatisfied [TDSA.V_RPT_T_MER_ADDN.MID_TAG] History [[TDSA.V_RPT_T_MER_ADDN.MID_TAG], [MID_TAG], [g0.midTag]], Access Pattern: Unsatisfied [TDSA.V_RPT_T_MER_ADDN.MID_GROUP] History [[TDSA.V_RPT_T_MER_ADDN.EXTERNAL_MID, TDSA.V_RPT_T_MER_ADDN.MID_GROUP], [MID_GROUP, EXTERNAL_MID], [g0.midGroup, g0.mid]]]
</message>
</error>
{code}
was:
When accessing a table that has an Access Pattern defined, the columns defined in the access pattern don't necessarily match the columns being exposed by the view.
I'm aliasing the output of the query with friendly column names, while the Access Pattern defines the access based on the real column names. When the user sees the Access Pattern warning message, it can be confusing as to what columns they actually need to supply.
> Access Pattern Messaging
> ------------------------
>
> Key: TEIID-4908
> URL: https://issues.jboss.org/browse/TEIID-4908
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.12.8.6_3
> Environment: JDV 6.3.2
> Windows 7
> Reporter: Steve Tran
> Assignee: Steven Hawkins
>
> When accessing a table that has an Access Pattern defined, the columns defined in the access pattern don't necessarily match the columns being exposed by the view.
> I'm aliasing the output of the query with friendly column names, while the Access Pattern defines the access based on the real column names. When the user sees the Access Pattern warning message, it can be confusing as to what columns they actually need to supply.
> Here's a real error message. In my view, I didn't define any of my columns with an underscore, I camel-cased everything.
> {code}
> <error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
> <code>TEIID30278</code>
> <message>
> TEIID30278 Group has an access pattern which has not been met: group(s) [TDSA.V_RPT_T_MER_ADDN]; access pattern(s) [Access Pattern: Unsatisfied [TDSA.V_RPT_T_MER_ADDN.MID_TAG] History [[TDSA.V_RPT_T_MER_ADDN.MID_TAG], [MID_TAG], [g0.midTag]], Access Pattern: Unsatisfied [TDSA.V_RPT_T_MER_ADDN.MID_GROUP] History [[TDSA.V_RPT_T_MER_ADDN.EXTERNAL_MID, TDSA.V_RPT_T_MER_ADDN.MID_GROUP], [MID_GROUP, EXTERNAL_MID], [g0.midGroup, g0.mid]]]
> </message>
> </error>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4908) Access Pattern Messaging
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIID-4908?page=com.atlassian.jira.plugin... ]
Steve Tran updated TEIID-4908:
------------------------------
Steps to Reproduce:
1) Define a source table with three columns: COL_A, COL_B, COL_C
2) Define a View with three columns : colA, colB, colC
3) Create an Access Pattern, with COL_A, and COL_B.
4) Add view to VDB and Deploy
5) Access VDB through OData. Only supply $filter=colA eq '123456' to break the access pattern rule.
6) The error message will list out the Access Pattern, but only use the true column names instead of colA or ColB.
> Access Pattern Messaging
> ------------------------
>
> Key: TEIID-4908
> URL: https://issues.jboss.org/browse/TEIID-4908
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.12.8.6_3
> Environment: JDV 6.3.2
> Windows 7
> Reporter: Steve Tran
> Assignee: Steven Hawkins
>
> When accessing a table that has an Access Pattern defined, the columns defined in the access pattern don't necessarily match the columns being exposed by the view.
> I'm aliasing the output of the query with friendly column names, while the Access Pattern defines the access based on the real column names. When the user sees the Access Pattern warning message, it can be confusing as to what columns they actually need to supply.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4908) Access Pattern Messaging
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIID-4908?page=com.atlassian.jira.plugin... ]
Steve Tran updated TEIID-4908:
------------------------------
Description:
When accessing a table that has an Access Pattern defined, the columns defined in the access pattern don't necessarily match the columns being exposed by the view.
I'm aliasing the output of the query with friendly column names, while the Access Pattern defines the access based on the real column names. When the user sees the Access Pattern warning message, it can be confusing as to what columns they actually need to supply.
> Access Pattern Messaging
> ------------------------
>
> Key: TEIID-4908
> URL: https://issues.jboss.org/browse/TEIID-4908
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.12.8.6_3
> Environment: JDV 6.3.2
> Windows 7
> Reporter: Steve Tran
> Assignee: Steven Hawkins
>
> When accessing a table that has an Access Pattern defined, the columns defined in the access pattern don't necessarily match the columns being exposed by the view.
> I'm aliasing the output of the query with friendly column names, while the Access Pattern defines the access based on the real column names. When the user sees the Access Pattern warning message, it can be confusing as to what columns they actually need to supply.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4908) Access Pattern Messaging
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIID-4908?page=com.atlassian.jira.plugin... ]
Steve Tran updated TEIID-4908:
------------------------------
Description: (was: I'm accessing my JDV table via OData4 through Salesforce's UI builder. The salesforce engine itself is creating the OData calls, and whenever a $filter is needed with multiple columns, it looks like salesforce pads the column name with a space in front and behind. That'll make the URL look like ...$filter={color:red}%20{color}ColumnA{color:red}%20{color}eq%20123%20and{color:red}%20{color}ColumnB{color:red}%20{color}eq...
The first space right after the $filter= throws off the JDV engine as it thinks it's a malformed URL - which I guess it is. The thing is when I tested it via the OData2 interface, it accepted it just fine. I'm not sure if the OData4 specifications explicitly state in terms of the URL, so it could be anybody's bug. Perhaps we could make JDV a little more forgiving and trim the spaces after un-URL-encoding the URI.)
> Access Pattern Messaging
> ------------------------
>
> Key: TEIID-4908
> URL: https://issues.jboss.org/browse/TEIID-4908
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.12.8.6_3
> Environment: JDV 6.3.2
> Windows 7
> Reporter: Steve Tran
> Assignee: Johnathon Lee
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4908) Access Pattern Messaging
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIID-4908?page=com.atlassian.jira.plugin... ]
Steve Tran updated TEIID-4908:
------------------------------
Component/s: (was: OData)
> Access Pattern Messaging
> ------------------------
>
> Key: TEIID-4908
> URL: https://issues.jboss.org/browse/TEIID-4908
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.12.8.6_3
> Environment: JDV 6.3.2
> Windows 7
> Reporter: Steve Tran
> Assignee: Johnathon Lee
>
> I'm accessing my JDV table via OData4 through Salesforce's UI builder. The salesforce engine itself is creating the OData calls, and whenever a $filter is needed with multiple columns, it looks like salesforce pads the column name with a space in front and behind. That'll make the URL look like ...$filter={color:red}%20{color}ColumnA{color:red}%20{color}eq%20123%20and{color:red}%20{color}ColumnB{color:red}%20{color}eq...
> The first space right after the $filter= throws off the JDV engine as it thinks it's a malformed URL - which I guess it is. The thing is when I tested it via the OData2 interface, it accepted it just fine. I'm not sure if the OData4 specifications explicitly state in terms of the URL, so it could be anybody's bug. Perhaps we could make JDV a little more forgiving and trim the spaces after un-URL-encoding the URI.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4908) Access Pattern Messaging
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIID-4908?page=com.atlassian.jira.plugin... ]
Steve Tran updated TEIID-4908:
------------------------------
Git Pull Request: (was: https://github.com/teiid/teiid/pull/948)
> Access Pattern Messaging
> ------------------------
>
> Key: TEIID-4908
> URL: https://issues.jboss.org/browse/TEIID-4908
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.12.8.6_3
> Environment: JDV 6.3.2
> Windows 7
> Reporter: Steve Tran
> Assignee: Johnathon Lee
>
> I'm accessing my JDV table via OData4 through Salesforce's UI builder. The salesforce engine itself is creating the OData calls, and whenever a $filter is needed with multiple columns, it looks like salesforce pads the column name with a space in front and behind. That'll make the URL look like ...$filter={color:red}%20{color}ColumnA{color:red}%20{color}eq%20123%20and{color:red}%20{color}ColumnB{color:red}%20{color}eq...
> The first space right after the $filter= throws off the JDV engine as it thinks it's a malformed URL - which I guess it is. The thing is when I tested it via the OData2 interface, it accepted it just fine. I'm not sure if the OData4 specifications explicitly state in terms of the URL, so it could be anybody's bug. Perhaps we could make JDV a little more forgiving and trim the spaces after un-URL-encoding the URI.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4908) Access Pattern Messaging
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIID-4908?page=com.atlassian.jira.plugin... ]
Steve Tran updated TEIID-4908:
------------------------------
Steps to Reproduce: (was: With Salesforce
- Build a VDB that has a table with a multi-column key
- In Salesforce, import the table via the OData importer
- Create a page in Salesforce that displays a few columns from that table
- Clicking on the a row in the salesforce UI will give you a drill-down, which will create a new URI to $filter down specifically on your one record. It'll create a filter with all the columns of the primary key
Without Salesforce
- Create a VDB
- Create a URI that has a space right after $filter=
e.g. http://localhost:8080/odata4/VDB/Schema/Table?$filter=%20ColumnA%20eq%207...)
> Access Pattern Messaging
> ------------------------
>
> Key: TEIID-4908
> URL: https://issues.jboss.org/browse/TEIID-4908
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.12.8.6_3
> Environment: JDV 6.3.2
> Windows 7
> Reporter: Steve Tran
> Assignee: Johnathon Lee
>
> I'm accessing my JDV table via OData4 through Salesforce's UI builder. The salesforce engine itself is creating the OData calls, and whenever a $filter is needed with multiple columns, it looks like salesforce pads the column name with a space in front and behind. That'll make the URL look like ...$filter={color:red}%20{color}ColumnA{color:red}%20{color}eq%20123%20and{color:red}%20{color}ColumnB{color:red}%20{color}eq...
> The first space right after the $filter= throws off the JDV engine as it thinks it's a malformed URL - which I guess it is. The thing is when I tested it via the OData2 interface, it accepted it just fine. I'm not sure if the OData4 specifications explicitly state in terms of the URL, so it could be anybody's bug. Perhaps we could make JDV a little more forgiving and trim the spaces after un-URL-encoding the URI.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years