[JBoss JIRA] (TEIID-225) LDAP Connector should use base DN for table as base DN for updates as well as queries
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-225?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-225.
----------------------------------
Resolution: Out of Date
Marking older issues as out of date.
> LDAP Connector should use base DN for table as base DN for updates as well as queries
> -------------------------------------------------------------------------------------
>
> Key: TEIID-225
> URL: https://issues.redhat.com/browse/TEIID-225
> Project: Teiid
> Issue Type: Feature Request
> Components: LDAP Connector
> Affects Versions: 6.0.0
> Environment: MetaMatrix 5.5.3RC2
> Reporter: Greg Haber
> Priority: Minor
> Fix For: Open To Community
>
>
> Ramesh had a great idea earlier today on the LDAP connector:
> [Ramesh] Why not search base info along with PK information to build the unique
> DN? That seems possible right?
> [Greg] Yes, that is a great idea! I will put in a JIRA for that (small code change, changing name of "search base" to just "base", and doc change). Probably we should have both relative and fully qualified DNs accepted here. Note however that the base may be several levels higher up in the tree then where you want to put the entry, so the base DN may be "ou=people,dc=company,dc=com", with a relative DN of "uid=ghaber,ou=newyork" here.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (TEIID-2123) Per model getMetadata() timeout
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-2123?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIID-2123.
-----------------------------------
Resolution: Out of Date
Marking older issues as out of date.
> Per model getMetadata() timeout
> -------------------------------
>
> Key: TEIID-2123
> URL: https://issues.redhat.com/browse/TEIID-2123
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Affects Versions: 8.0
> Reporter: Mark Addleman
> Priority: Minor
> Fix For: Open To Community
>
>
> A way of specifying, per model, a timeout for the getMetadata() call. The timeout should be processed in such a way that delegating translators have an opportunity to intercept the interruption and, potentially, supply default metadata. I think the normal Thread.interrupt() approach should work.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months