[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)
9 years, 8 months
[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)
9 years, 8 months
[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)
9 years, 8 months
[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)
9 years, 8 months
[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)
9 years, 8 months
[JBoss JIRA] (TEIID-3383) Add NPE handling in WSConnectionImpl.invoke
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3383?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3383.
---------------------------------
> Add NPE handling in WSConnectionImpl.invoke
> -------------------------------------------
>
> Key: TEIID-3383
> URL: https://issues.jboss.org/browse/TEIID-3383
> Project: Teiid
> Issue Type: Bug
> Components: Connector API
> Affects Versions: 8.4.1
> Reporter: Bas Piepers
> Assignee: Steven Hawkins
> Priority: Minor
>
> In the WSConnectionImpl.java class in the org.teiid.resource.adapter.ws package (of connector-ws-8.4.1-redhat-9.jar) in the invoke(DataSource ds) method at the end it tries to get the content-type from the response in line 164 and then returns the first item in the list of content types:
> ArrayList contentTypes = (ArrayList)this.responseContext.get("content-type"); //$NON-NLS-1$
> return new HttpDataSource(url, (InputStream)response.getEntity(), (String)contentTypes.get(0));
> However if the web service that it calls returns an error code (like 415, for example) it does not always contain a content-type in its header. Basically this method expects a result to be returned all the time with a corresponding content-type which is not right. The line where it calls contentTypes.get(0) may result in a NPE.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 8 months