April 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3412) Change MS Access to use jackcess, since ODBC-JDBC bridge is removed in JDK 1.8

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3412?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-3412: ------------------------------------ > looks like an active project with active commit log Yes, I have repost a issue, they give me quick response as [1], but UcanAccess only for MS Access, if we consider "ODBC" source in general, it not a option. [1] http://sourceforge.net/p/ucanaccess/discussion/general/thread/58e4e3c9/ > Change MS Access to use jackcess, since ODBC-JDBC bridge is removed in JDK 1.8 > ------------------------------------------------------------------------------ > > Key: TEIID-3412 > URL: https://issues.jboss.org/browse/TEIID-3412 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Kylin Soong > > In JDK 1.8, the ODBC-JDBC bridge is removed, so accessing MS Access using this method will not be available. An alternative, open source, driver that can be used is: http://jackcess.sourceforge.net > In nexus: > <dependency> > <groupId>com.healthmarketscience.jackcess</groupId> > <artifactId>jackcess</artifactId> > <version>2.0.9</version> > </dependency> > This may require a new translator, but won't be know until a deeper look is done. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3422) Setting more than 513MB for buffer-service-max-storage-object-size, OOME occurs at org.teiid.common.buffer.impl.BufferFrontedFileStoreCache.initialize()

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3422?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3422: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1210577 > Setting more than 513MB for buffer-service-max-storage-object-size, OOME occurs at org.teiid.common.buffer.impl.BufferFrontedFileStoreCache.initialize() > -------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-3422 > URL: https://issues.jboss.org/browse/TEIID-3422 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Environment: JBoss DV 6.0, 6.1 > Reporter: hisao furuichi > Assignee: Steven Hawkins > > Setting more than 513MB for buffer-service-max-storage-object-size, OOME occurs at org.teiid.common.buffer.impl.BufferFrontedFileStoreCache.initialize(). > One of our user needs to set more than 512MB for buffer-service-max-storage-object-size to avoid TEIID30001[1], this limitation becomes a critical issue for them. > Additional Information: > By taking look at the source code[2], if the value of maxStorageObjectSize is more than equals with 536870912, the loop becomes infinit, and will cause OOME. > [1] > TEIID30001 Max block number exceeded by 233,144 21,422,155. Increase the maxStorageObjectSize to support larger storage objects. Alternatively you could make the processor batch size smaller. > [2]teiid/engine/src/main/java/org/teiid/common/buffer/impl/BufferFrontedFileStoreCache.java > === > public static final long MAX_ADDRESSABLE_MEMORY = 1l<<(ADDRESS_BITS+LOG_BLOCK_SIZE); > ~~ > static final int BLOCK_SIZE = 1 << LOG_BLOCK_SIZE; > ~~ > public void initialize() throws TeiidComponentException { > ~~ > List<BlockStore> stores = new ArrayList<BlockStore>(); > int size = BLOCK_SIZE; > int files = 32; //this allows us to have 64 terabytes of smaller block sizes > do { > stores.add(new BlockStore(this.storageManager, size, 30, files)); > size <<=1; > if (files > 1) { > files >>= 1; > } > } while ((size>>1) < maxStorageObjectSize); > ~~ > === -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3422) Setting more than 513MB for buffer-service-max-storage-object-size, OOME occurs at org.teiid.common.buffer.impl.BufferFrontedFileStoreCache.initialize()

by hisao furuichi (JIRA)

hisao furuichi created TEIID-3422: ------------------------------------- Summary: Setting more than 513MB for buffer-service-max-storage-object-size, OOME occurs at org.teiid.common.buffer.impl.BufferFrontedFileStoreCache.initialize() Key: TEIID-3422 URL: https://issues.jboss.org/browse/TEIID-3422 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.7 Environment: JBoss DV 6.0, 6.1 Reporter: hisao furuichi Assignee: Steven Hawkins Setting more than 513MB for buffer-service-max-storage-object-size, OOME occurs at org.teiid.common.buffer.impl.BufferFrontedFileStoreCache.initialize(). One of our user needs to set more than 512MB for buffer-service-max-storage-object-size to avoid TEIID30001[1], this limitation becomes a critical issue for them. Additional Information: - By taking look at the source code[2], if the value of maxStorageObjectSize is more than equals with 536870912, the loop becomes infinit, and will cause OOME. [1] TEIID30001 Max block number exceeded by 233,144 21,422,155. Increase the maxStorageObjectSize to support larger storage objects. Alternatively you could make the processor batch size smaller. [2]teiid/engine/src/main/java/org/teiid/common/buffer/impl/BufferFrontedFileStoreCache.java === public static final long MAX_ADDRESSABLE_MEMORY = 1l<<(ADDRESS_BITS+LOG_BLOCK_SIZE); ~~ static final int BLOCK_SIZE = 1 << LOG_BLOCK_SIZE; ~~ public void initialize() throws TeiidComponentException { ~~ List<BlockStore> stores = new ArrayList<BlockStore>(); int size = BLOCK_SIZE; int files = 32; //this allows us to have 64 terabytes of smaller block sizes do { stores.add(new BlockStore(this.storageManager, size, 30, files)); size <<=1; if (files > 1) { files >>= 1; } } while ((size>>1) < maxStorageObjectSize); ~~ === -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3422) Setting more than 513MB for buffer-service-max-storage-object-size, OOME occurs at org.teiid.common.buffer.impl.BufferFrontedFileStoreCache.initialize()

by hisao furuichi (JIRA)

[ https://issues.jboss.org/browse/TEIID-3422?page=com.atlassian.jira.plugin... ] hisao furuichi updated TEIID-3422: ---------------------------------- Description: Setting more than 513MB for buffer-service-max-storage-object-size, OOME occurs at org.teiid.common.buffer.impl.BufferFrontedFileStoreCache.initialize(). One of our user needs to set more than 512MB for buffer-service-max-storage-object-size to avoid TEIID30001[1], this limitation becomes a critical issue for them. Additional Information: By taking look at the source code[2], if the value of maxStorageObjectSize is more than equals with 536870912, the loop becomes infinit, and will cause OOME. [1] TEIID30001 Max block number exceeded by 233,144 21,422,155. Increase the maxStorageObjectSize to support larger storage objects. Alternatively you could make the processor batch size smaller. [2]teiid/engine/src/main/java/org/teiid/common/buffer/impl/BufferFrontedFileStoreCache.java === public static final long MAX_ADDRESSABLE_MEMORY = 1l<<(ADDRESS_BITS+LOG_BLOCK_SIZE); ~~ static final int BLOCK_SIZE = 1 << LOG_BLOCK_SIZE; ~~ public void initialize() throws TeiidComponentException { ~~ List<BlockStore> stores = new ArrayList<BlockStore>(); int size = BLOCK_SIZE; int files = 32; //this allows us to have 64 terabytes of smaller block sizes do { stores.add(new BlockStore(this.storageManager, size, 30, files)); size <<=1; if (files > 1) { files >>= 1; } } while ((size>>1) < maxStorageObjectSize); ~~ === was: Setting more than 513MB for buffer-service-max-storage-object-size, OOME occurs at org.teiid.common.buffer.impl.BufferFrontedFileStoreCache.initialize(). One of our user needs to set more than 512MB for buffer-service-max-storage-object-size to avoid TEIID30001[1], this limitation becomes a critical issue for them. Additional Information: - By taking look at the source code[2], if the value of maxStorageObjectSize is more than equals with 536870912, the loop becomes infinit, and will cause OOME. [1] TEIID30001 Max block number exceeded by 233,144 21,422,155. Increase the maxStorageObjectSize to support larger storage objects. Alternatively you could make the processor batch size smaller. [2]teiid/engine/src/main/java/org/teiid/common/buffer/impl/BufferFrontedFileStoreCache.java === public static final long MAX_ADDRESSABLE_MEMORY = 1l<<(ADDRESS_BITS+LOG_BLOCK_SIZE); ~~ static final int BLOCK_SIZE = 1 << LOG_BLOCK_SIZE; ~~ public void initialize() throws TeiidComponentException { ~~ List<BlockStore> stores = new ArrayList<BlockStore>(); int size = BLOCK_SIZE; int files = 32; //this allows us to have 64 terabytes of smaller block sizes do { stores.add(new BlockStore(this.storageManager, size, 30, files)); size <<=1; if (files > 1) { files >>= 1; } } while ((size>>1) < maxStorageObjectSize); ~~ === > Setting more than 513MB for buffer-service-max-storage-object-size, OOME occurs at org.teiid.common.buffer.impl.BufferFrontedFileStoreCache.initialize() > -------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-3422 > URL: https://issues.jboss.org/browse/TEIID-3422 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Environment: JBoss DV 6.0, 6.1 > Reporter: hisao furuichi > Assignee: Steven Hawkins > > Setting more than 513MB for buffer-service-max-storage-object-size, OOME occurs at org.teiid.common.buffer.impl.BufferFrontedFileStoreCache.initialize(). > One of our user needs to set more than 512MB for buffer-service-max-storage-object-size to avoid TEIID30001[1], this limitation becomes a critical issue for them. > Additional Information: > By taking look at the source code[2], if the value of maxStorageObjectSize is more than equals with 536870912, the loop becomes infinit, and will cause OOME. > [1] > TEIID30001 Max block number exceeded by 233,144 21,422,155. Increase the maxStorageObjectSize to support larger storage objects. Alternatively you could make the processor batch size smaller. > [2]teiid/engine/src/main/java/org/teiid/common/buffer/impl/BufferFrontedFileStoreCache.java > === > public static final long MAX_ADDRESSABLE_MEMORY = 1l<<(ADDRESS_BITS+LOG_BLOCK_SIZE); > ~~ > static final int BLOCK_SIZE = 1 << LOG_BLOCK_SIZE; > ~~ > public void initialize() throws TeiidComponentException { > ~~ > List<BlockStore> stores = new ArrayList<BlockStore>(); > int size = BLOCK_SIZE; > int files = 32; //this allows us to have 64 terabytes of smaller block sizes > do { > stores.add(new BlockStore(this.storageManager, size, 30, files)); > size <<=1; > if (files > 1) { > files >>= 1; > } > } while ((size>>1) < maxStorageObjectSize); > ~~ > === -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3270) Allow UDFs to call Teiid functions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3270?page=com.atlassian.jira.plugin... ] Work on TEIID-3270 started by Steven Hawkins. --------------------------------------------- > Allow UDFs to call Teiid functions > ---------------------------------- > > Key: TEIID-3270 > URL: https://issues.jboss.org/browse/TEIID-3270 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Sanjeev Gour > Assignee: Steven Hawkins > Fix For: 8.11 > > > Currently custom functions require the implementation on be in Java, there could be an alternative way to allow using Teiid expressions inside the custom functions. The related thread is here- > https://developer.jboss.org/thread/251179 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3419) Add ability to set a default role across all VDBs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3419?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3419: --------------------------------------- Also the notion of a default role doesn't work very well when vdbs are in different security domains as the mapped role names will can be different. So please determine from the customer what if a flag to prevent deployment if data roles are not enabled is sufficient? We wouldn't be doing further validation on what the data roles were defined as, just if they exist. > Add ability to set a default role across all VDBs > ------------------------------------------------- > > Key: TEIID-3419 > URL: https://issues.jboss.org/browse/TEIID-3419 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Marc Shirley > Assignee: Steven Hawkins > > There should be an ability to either set a default role across the server, or to restrict access by default. For example, all VDBs have a default user role that is applied before the VDB specific roles are. Alternatively, there could be a system wide flag that toggles the behavior of VDBs when no roles are defined between accessible to all or denied to all. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3420) Support insert/update with ldap multi-value concat

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3420?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3420. ----------------------------------- Resolution: Done Modified the insert/update to expect the concat format and updated the docs. > Support insert/update with ldap multi-value concat > --------------------------------------------------- > > Key: TEIID-3420 > URL: https://issues.jboss.org/browse/TEIID-3420 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > The translator currently only supports multi-value concat in the context of reads. Insert/update should be supported as well. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3411) LDAP translator and multi-valued arrays

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3411?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3411. ----------------------------------- Resolution: Done Added read support. But did not address insert/update/delete - which would require a lot more handling to support. > LDAP translator and multi-valued arrays > --------------------------------------- > > Key: TEIID-3411 > URL: https://issues.jboss.org/browse/TEIID-3411 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 8.11 > > > The problem is with how multi-valued attribute from the LDAP response is handled. They don't want to have the data mapped to an array or multivalued-concat and then transformed into another table to get the unique values. There is an issue with the translator as it should handle multivalued attribute, by simply creating multiple rows for each value of the multivalued attribute. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3421) Add ability to create Teiid language based custom functions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3421?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3421. ----------------------------------- Resolution: Duplicate Issue Duplicate of TEIID-3270 > Add ability to create Teiid language based custom functions > ----------------------------------------------------------- > > Key: TEIID-3421 > URL: https://issues.jboss.org/browse/TEIID-3421 > Project: Teiid > Issue Type: Feature Request > Reporter: Marc Shirley > Assignee: Steven Hawkins > > Add the capability to create user defined functions that do not require Java backing. Use case would be something like a library of string manipulation functions such as separating a username or domain from an email address. For example: > BEGIN > SELECT substring(inputValue, 0, (locate('@', inputValue) - 1)) AS username; > END > Once the function is defined in the function library model, the user would then be able to utilize the functions in ad hoc queries like the below: > SELECT getUsername(email) as username ... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3421) Add ability to create Teiid language based custom functions

by Marc Shirley (JIRA)

Marc Shirley created TEIID-3421: ----------------------------------- Summary: Add ability to create Teiid language based custom functions Key: TEIID-3421 URL: https://issues.jboss.org/browse/TEIID-3421 Project: Teiid Issue Type: Feature Request Reporter: Marc Shirley Assignee: Steven Hawkins Add the capability to create user defined functions that do not require Java backing. Use case would be something like a library of string manipulation functions such as separating a username or domain from an email address. For example: BEGIN SELECT substring(inputValue, 0, (locate('@', inputValue) - 1)) AS username; END Once the function is defined in the function library model, the user would then be able to utilize the functions in ad hoc queries like the below: SELECT getUsername(email) as username ... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2015