[JBoss JIRA] (TEIID-3215) External Materialization ON_VDB_START_SCRIPT invocation issues
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3215?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3215:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1163685|https://bugzilla.redhat.com/show_bug.cgi?id=1163685] from NEW to MODIFIED
> External Materialization ON_VDB_START_SCRIPT invocation issues
> --------------------------------------------------------------
>
> Key: TEIID-3215
> URL: https://issues.jboss.org/browse/TEIID-3215
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7
> Reporter: Jan Stastny
> Assignee: Ramesh Reddy
> Labels: Final
> Fix For: 8.7.1, 8.9
>
>
> With materialized view I have set teiid_rel:ON_VDB_START_SCRIPT property for the external matview table. (Simple query to increment a column in table to count invocations.)
> Invocation of the script is dependent upon the way the vdb is deployed. The first case (A) doesn't invoke the script, the second (B) does.
> A - 1. Copy the vdbname-vdb.xml into deployments folder
> 2. Start the server
> B - 1. Start the server
> 2. Copy the vdbname-vdb.xml into deployments folder
> That means that after server stop (maintenance) the script is not invoked on start, which can cause problems when the script is used to initialize running environment (clear table, create temporary table natively,...)
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (TEIID-3220) Datafederation quick start needs materialization teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT changed to match docs
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3220?page=com.atlassian.jira.plugin... ]
Work on TEIID-3220 started by Van Halbert.
------------------------------------------
> Datafederation quick start needs materialization teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT changed to match docs
> -----------------------------------------------------------------------------------------------------------
>
> Key: TEIID-3220
> URL: https://issues.jboss.org/browse/TEIID-3220
> Project: Teiid
> Issue Type: Enhancement
> Components: Quick Starts
> Affects Versions: 8.7.1, 8.10
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Minor
>
> The data federation quick start does not demonstrate the same way of loading in the materialized table by executing multiple statements when "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" is performed, as the doc's do (based on the latest changes).
> It should now use the following to work like the doc's prescribe:
> "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'execute accounts.native(''ALTER TABLE h2_stock_mat RENAME TO h2_stock_mat_temp'');execute accounts.native(''ALTER TABLE mat_stock_staging RENAME TO h2_stock_mat'');execute accounts.native(''ALTER TABLE h2_stock_mat_temp RENAME TO mat_stock_staging'');',
>
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (TEIID-3220) Datafederation quick start needs materialization teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT changed to match docs
by Van Halbert (JIRA)
Van Halbert created TEIID-3220:
----------------------------------
Summary: Datafederation quick start needs materialization teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT changed to match docs
Key: TEIID-3220
URL: https://issues.jboss.org/browse/TEIID-3220
Project: Teiid
Issue Type: Enhancement
Components: Quick Starts
Affects Versions: 8.7.1, 8.10
Reporter: Van Halbert
Assignee: Van Halbert
Priority: Minor
The data federation quick start does not demonstrate the same way of loading in the materialized table by executing multiple statements when "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" is performed, as the doc's do (based on the latest changes).
It should now use the following to work like the doc's prescribe:
"teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'execute accounts.native(''ALTER TABLE h2_stock_mat RENAME TO h2_stock_mat_temp'');execute accounts.native(''ALTER TABLE mat_stock_staging RENAME TO h2_stock_mat'');execute accounts.native(''ALTER TABLE h2_stock_mat_temp RENAME TO mat_stock_staging'');',
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (TEIID-3215) External Materialization ON_VDB_START_SCRIPT invocation issues
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3215?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-3215.
---------------------------------
Labels: Final (was: )
Resolution: Done
The ON_VDB_START_SCRIPT will be executed when
* vdb deploys
* every time server restarts
Recommendation to VDB developers is to make sure the script in written such a way that it accounts for server restarts. Like
{code}
IF EXISTS ...
{code}
examples http://stackoverflow.com/questions/1109061/insert-on-duplicate-update-in-...
> External Materialization ON_VDB_START_SCRIPT invocation issues
> --------------------------------------------------------------
>
> Key: TEIID-3215
> URL: https://issues.jboss.org/browse/TEIID-3215
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7
> Reporter: Jan Stastny
> Assignee: Ramesh Reddy
> Labels: Final
> Fix For: 8.7.1, 8.9
>
>
> With materialized view I have set teiid_rel:ON_VDB_START_SCRIPT property for the external matview table. (Simple query to increment a column in table to count invocations.)
> Invocation of the script is dependent upon the way the vdb is deployed. The first case (A) doesn't invoke the script, the second (B) does.
> A - 1. Copy the vdbname-vdb.xml into deployments folder
> 2. Start the server
> B - 1. Start the server
> 2. Copy the vdbname-vdb.xml into deployments folder
> That means that after server stop (maintenance) the script is not invoked on start, which can cause problems when the script is used to initialize running environment (clear table, create temporary table natively,...)
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (TEIID-3215) External Materialization ON_VDB_START_SCRIPT invocation issues
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3215?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-3215:
--------------------------------
Fix Version/s: 8.7.1
8.9
Tester: Jan Stastny
Assignee: Ramesh Reddy (was: Steven Hawkins)
Workaround Description: Only deploy the VDB to the running server, not copy to the directory and start the server
Workaround: Workaround Exists
Estimated Difficulty: Low
Component/s: Server
Affects: Documentation (Ref Guide, User Guide, etc.)
> External Materialization ON_VDB_START_SCRIPT invocation issues
> --------------------------------------------------------------
>
> Key: TEIID-3215
> URL: https://issues.jboss.org/browse/TEIID-3215
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7
> Reporter: Jan Stastny
> Assignee: Ramesh Reddy
> Fix For: 8.7.1, 8.9
>
>
> With materialized view I have set teiid_rel:ON_VDB_START_SCRIPT property for the external matview table. (Simple query to increment a column in table to count invocations.)
> Invocation of the script is dependent upon the way the vdb is deployed. The first case (A) doesn't invoke the script, the second (B) does.
> A - 1. Copy the vdbname-vdb.xml into deployments folder
> 2. Start the server
> B - 1. Start the server
> 2. Copy the vdbname-vdb.xml into deployments folder
> That means that after server stop (maintenance) the script is not invoked on start, which can cause problems when the script is used to initialize running environment (clear table, create temporary table natively,...)
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (TEIID-3200) Teiid 8.8.1 embedded version doesn't work with IBM JDK 6
by Ivan Chan (JIRA)
[ https://issues.jboss.org/browse/TEIID-3200?page=com.atlassian.jira.plugin... ]
Ivan Chan commented on TEIID-3200:
----------------------------------
I haven't tried with 5.2.8/ 5.2.10 yet. I am using 5.1.2 with Teiid 8.8.1. And it seems to work. I will try out the other 2 version later. Thanks.
> 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.8#6338)
11 years, 4 months
[JBoss JIRA] (TEIID-3192) Migrate Salesforce connectivity to sf partner api jars
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3192?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3192:
---------------------------------------
I'm looking at adding the proxy config as proper config settings on the resource adapter - so that the password can be handled with as/eap password management. There are quite a few other options though. It may make sense to support just a generic properties file/string also as a catch all.
> Migrate Salesforce connectivity to sf partner api jars
> ------------------------------------------------------
>
> Key: TEIID-3192
> URL: https://issues.jboss.org/browse/TEIID-3192
> Project: Teiid
> Issue Type: Component Upgrade
> Components: Salesforce Connector
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.10
>
>
> There are several deficiencies in using CXF for salesforce connectivity - we are not batching correctly, there is additional CXF overhead, and we have to maintain our own generated java of the api.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 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 commented on TEIID-3200:
---------------------------------------
Can you confirm if 5.2.8 works for 8.8.1 or if 5.2.10 works in Teiid 8.9?
> 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.8#6338)
11 years, 4 months