April 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3259) dynamic sql cannot use into with updates

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3259?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3259. --------------------------------- > dynamic sql cannot use into with updates > ---------------------------------------- > > Key: TEIID-3259 > URL: https://issues.jboss.org/browse/TEIID-3259 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.9 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9.1, 8.10 > > > TEIID-3198 refined the dynamic sql handling such that the use of AS columns required a result set from the query. However our materialization logic in SYSADMIN and our documentation indicated that the approach should be used. We may need to offer backward compatibility and at the very least should update the materialization sql. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3233) Getting NPE in test integration when calling AdminFactory.getDomainAwareList

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3233?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3233. --------------------------------- > Getting NPE in test integration when calling AdminFactory.getDomainAwareList > ---------------------------------------------------------------------------- > > Key: TEIID-3233 > URL: https://issues.jboss.org/browse/TEIID-3233 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1, 9.x > Reporter: Van Halbert > Assignee: Steven Hawkins > > When getVDB's is being called in AdminFactory, an NPE occurs. Here's the diff for the fix: > try { > ModelNode outcome = this.connection.execute(request); > if (Util.isSuccess(outcome)) { > - return getDomainAwareList(outcome, VDBMetadataMapper.INSTANCE); > + List<VDBMetaData> list = getDomainAwareList(outcome, VDBMetadataMapper.INSTANCE); > + if (list != null) { > + return list; > + } > } > } catch (IOException e) { -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3138) EmbeddedServer does not shutdown the session monitor

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3138?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3138. --------------------------------- > EmbeddedServer does not shutdown the session monitor > ---------------------------------------------------- > > Key: TEIID-3138 > URL: https://issues.jboss.org/browse/TEIID-3138 > Project: Teiid > Issue Type: Bug > Components: Embedded > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9 > > > The session service has a timer thread which should be shutdown when the embedded server is shutdown. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3250) Rewritten unknown expression in select becomes false

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3250?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3250. --------------------------------- > Rewritten unknown expression in select becomes false > ---------------------------------------------------- > > Key: TEIID-3250 > URL: https://issues.jboss.org/browse/TEIID-3250 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9.1, 8.10 > > > select 1 = null > will be rewritten as > select false > it should instead be > select null -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2992) MongoDB: Offset clause causes MongoDB to crash

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2992?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2992. --------------------------------- > MongoDB: Offset clause causes MongoDB to crash > ---------------------------------------------- > > Key: TEIID-2992 > URL: https://issues.jboss.org/browse/TEIID-2992 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4.1 > Environment: MongoDB < 2.5.2 > Reporter: Filip Elias > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.8, 8.7.1 > > > MongoDB(version < 2.5.2) will crash when offset clause is used in SQL query. > Althought the bug[1] is in MongoDB (Adding big number into $limit causes Mongodb to shutdown), it is also caused by teiid because it adds max integer into $limit which seems to be unnecessary. > Sample query: > {code} > SELECT INTKEY FROM bqt1.smalla ORDER BY INTKEY OFFSET 45 ROWS > {code} > Generated mongo command: > {code} > { aggregate: "smalla", pipeline: [ { $project: { c_0: "$INTKEY" } }, { $sort: { c_0: 1 } }, { $skip: 45 }, { $limit: 2147483647 } ] } > {code} > [1] https://jira.mongodb.org/browse/SERVER-10136 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3400) Oracle connection not consistently usable after cancel

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3400?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3400: ---------------------------------- Fix Version/s: 8.10.1 > Oracle connection not consistently usable after cancel > ------------------------------------------------------ > > Key: TEIID-3400 > URL: https://issues.jboss.org/browse/TEIID-3400 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Affects Versions: 8.10 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10.1, 8.11 > > > With TEIID-3275 we made use of cancel calls more to ensure that cleanup was happening as quickly as possible. However Oracle JDBC has a bug (independently reproducible outside Teiid) where if the cancelled statement does not reach the point of thrown an exception related to the cancel, then the next statement from that connection will throw the exception. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3388) Different null ordering for float and double numbers with RADIANS function (Oracle 12)

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3388?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3388. --------------------------------- > Different null ordering for float and double numbers with RADIANS function (Oracle 12) > -------------------------------------------------------------------------------------- > > Key: TEIID-3388 > URL: https://issues.jboss.org/browse/TEIID-3388 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Attachments: server_ora10.log, server_ora12.log > > > Queries: > 1. SELECT RADIANS(DoubleNum) FROM BQT1.SmallA ORDER BY DoubleNum; > 2. SELECT RADIANS(FloatNum) FROM BQT1.SmallA ORDER BY FloatNum; > Both queries return different null ordering. In case of DoubleNum nulls are first. In the second case nulls are last records. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3056) MongoDB: Put nested JSON documents in one single table

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3056?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3056. --------------------------------- > MongoDB: Put nested JSON documents in one single table > ------------------------------------------------------- > > Key: TEIID-3056 > URL: https://issues.jboss.org/browse/TEIID-3056 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7 > Environment: MongoDB with Teiid > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Labels: teiid > > Currently, it seems like ID needs to be appear in parent and child for nested documents. But it is unlikely a case for MongoDB customers. It would be nice if Teiid can flatten out data in one single table. Therefore, users would not need to insert parent id in the child document in order for Teiid to work. > I am thinking the following case. For example I have a JSON object like this: > {code} > Customer > { > _id: 1374932, > FirstName: "John", > LastName: "Doe", > Address: { > _id: 43839430, > Street: "123 Lane", > City: "New York", > State: "NY", > Zipcode: "12345" > } > } > {code} > > In this case, customer._id doesn't exist inside Address. There is no way to do join in regular SQL fashion. But it would be nice if teiid can put the column from parent and child into a single table. Maybe something similar to the following schema: > {code} > CREATE FOREIGN TABLE Customer ( > CustomerId integer PRIMARY KEY, > FirstName varchar(25), > LastName varchar(25), > address__id integer, > address_Street varchar(50), > address_City varchar(25), > address_State varchar(25), > address_Zipcode varchar(6), > ) OPTIONS(UPDATABLE 'TRUE'); > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3232) Embedded dist zip for 8.9.0 is missing from repo

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3232?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3232. --------------------------------- > Embedded dist zip for 8.9.0 is missing from repo > ------------------------------------------------ > > Key: TEIID-3232 > URL: https://issues.jboss.org/browse/TEIID-3232 > Project: Teiid > Issue Type: Bug > Components: Build/Kits, Embedded > Affects Versions: 8.9 > Environment: Java version: 1.7.0_71, vendor: Oracle Corporation > Java home: C:\Program Files\Java\jdk1.7.0_71\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" > Ant 1.9.4 > Ivy 2.3.0 > Reporter: Gary Gregory > Assignee: Steven Hawkins > Priority: Blocker > > For version 8.8.1, our build uses > https://repository.jboss.org/org/jboss/teiid/teiid/8.8.1/teiid-8.8.1-embe... > There is no such zip for 8.9.0. > In fact there are no useful files in https://repository.jboss.org/org/jboss/teiid/teiid/8.9.0.Final > Help! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3200) Teiid 8.8.1 embedded version doesn't work with IBM JDK 6

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3200?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3200. --------------------------------- > Teiid 8.8.1 embedded version doesn't work with IBM JDK 6 > -------------------------------------------------------- > > Key: TEIID-3200 > URL: https://issues.jboss.org/browse/TEIID-3200 > Project: Teiid > Issue Type: Bug > Components: Embedded > Affects Versions: 8.8 > Environment: Running Teiid 8.8.1 with IBM JDK 6 > Reporter: Ivan Chan > Assignee: Steven Hawkins > Labels: teiid > > Teiid 8.7 used to work with IBM JDK 6, but not Teiid 8.8.1. > It causes the following error: > [java] Caused by: org.infinispan.CacheException: Unable to invoke method public void org.infinispan.commands.CommandsFactoryImpl.setupDependencies(org.infinispan.container.DataContainer,org.infinispan.notifications.cachelistener.CacheNotifier,org.infinispan.Cache,org.infinispan.interceptors.InterceptorChain,org.infinispan.distribution.DistributionManager,org.infinispan.context.InvocationContextContainer,org.infinispan.transaction.TransactionTable,org.infinispan.configuration.cache.Configuration,java.util.Map,org.infinispan.transaction.xa.recovery.RecoveryManager,org.infinispan.statetransfer.StateProvider,org.infinispan.statetransfer.StateConsumer,org.infinispan.util.concurrent.locks.LockManager,org.infinispan.container.InternalEntryFactory,org.infinispan.distexec.mapreduce.MapReduceManager,org.infinispan.statetransfer.StateTransferManager,org.infinispan.xsite.BackupSender,org.infinispan.commands.CancellationService) on object of type CommandsFactoryImpl with parameters [org.infinispan.container.DefaultDataContainer@189b189b, org.infinispan.notifications.cachelistener.CacheNotifierImpl@400e400e, Cache 'resultset'@43084308, > [java] >> org.infinispan.interceptors.InvocationContextInterceptor, null, org.infinispan.context.TransactionalInvocationContextContainer@3050305, org.infinispan.transaction.TransactionTable@54695469, Configuration{classLoader=null, clustering=ClusteringConfiguration{async=AsyncConfiguration{asyncMarshalling=false, replicationQueue=null, replicationQueueInterval=5000, replicationQueueMaxElements=1000, useReplicationQueue=false}, cacheMode=LOCAL, hash=HashConfiguration{consistentHashFactory=null, hash=MurmurHash3, numOwners=2, numSegments=60, groupsConfiguration=GroupsConfiguration{enabled=false, groupers=[]}, stateTransferConfiguration=StateTransferConfiguration{chunkSize=10000, fetchInMemoryState=false, originalFetchInMemoryState=null, timeout=240000, awaitInitialTransfer=false, originalAwaitInitialTransfer=null}}, l1=L1Configuration{enabled=false, invalidationThreshold=0, lifespan=600000, onRehash=false, cleanupTaskFrequency=600000}, stateTransfer=StateTransferConfiguration{chunkSize=10000, fetchInMemoryState=false, originalFetchInMemoryState=null, timeout=240000, awaitInitialTransfer=false, originalAwaitInitialTransfer=null}, sync=SyncConfiguration{replTimeout=15000}}, customInterceptors=CustomInterceptorsConfiguration{interceptors=[]}, dataContainer=DataContainerConfiguration{dataContainer=null}, deadlockDetection=DeadlockDetectionConfiguration{enabled=false, spinDuration=100}, eviction=EvictionConfiguration{maxEntries=1024, strategy=LIRS, threadPolicy=DEFAULT}, expiration=ExpirationConfiguration{lifespan=7200000, maxIdle=-1, reaperEnabled=true, wakeUpInterval=60000}, indexing=IndexingConfiguration{enabled=false, indexLocalOnly=false}, invocationBatching=InvocationBatchingConfiguration{enabled=false}, jmxStatistics=JMXStatisticsConfiguration{enabled=false}, loaders=LoadersConfiguration{cacheLoaders=[], passivation=false, preload=false, shared=false}, locking=LockingConfiguration{concurrencyLevel=32, isolationLevel=READ_COMMITTED, lockAcquisitionTimeout=10000, useLockStriping=false, writeSkewCheck=false}, modules={}, storeAsBinary=StoreAsBinaryConfiguration{enabled=false, storeKeysAsBinary=true, storeValuesAsBinary=true}, transaction=TransactionConfiguration{autoCommit=true, cacheStopTimeout=30000, eagerLockingSingleNode=false, lockingMode=OPTIMISTIC, syncCommitPhase=true, syncRollbackPhase=false, transactionManagerLookup=org.infinispan.transaction.lookup.GenericTransactionManagerLookup@4da54da5, transactionSynchronizationRegistryLookup=null, transactionMode=TRANSACTIONAL, useEagerLocking=false, useSynchronization=true, recovery=RecoveryConfiguration{enabled=true, recoveryInfoCacheName='__recoveryInfoCacheName__'}, reaperWakeUpInterval=1000, completedTxTimeout=15000, use1PcForAutoCommitTransactions=false}, versioning=VersioningConfiguration{enabled=false, scheme=NONE}, unsafe=UnsafeConfiguration{unreliableReturnValues=false}, sites=SiteConfiguration{allBackups=[], backupFor=BackupForConfiguration{remoteCache='null', remoteSite='null'}, disableBackups=false, inUseBackupSites=[]}}, {}, {}, null, null, org.infinispan.util.concurrent.locks.LockManagerImpl@15b815b8, org.infinispan.container.InternalEntryFactoryImpl@1c921c92, org.infinispan.distexec.mapreduce.MapReduceManagerImpl@6e906e90, null, org.infinispan.xsite.BackupSenderImpl@39643964, org.infinispan.commands.CancellationServiceImpl@2ec52ec5] > Actually, this is a bug in infinispan. > https://issues.jboss.org/browse/ISPN-3611 > This bug got introduced after upgrading infinspan-core version from 5.1.2 to 5.2.7 in Teiid 8.8.1. > Maybe Teiid should consider to upgrade infinspan-core to version 6.0 instead. -- 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