[JBoss JIRA] (TEIID-4192) If a column is blank the TEXTAGG function excludes it from the output
by Debbie Steigner (JIRA)
Debbie Steigner created TEIID-4192:
--------------------------------------
Summary: If a column is blank the TEXTAGG function excludes it from the output
Key: TEIID-4192
URL: https://issues.jboss.org/browse/TEIID-4192
Project: Teiid
Issue Type: Bug
Affects Versions: 8.7.5.6_2
Reporter: Debbie Steigner
Assignee: Steven Hawkins
If a column value is blank, it is excluding it in the result, causing incorrect output.
TEXTAGG(FOR Last_Name,
First_Name,
Middle_initial,
Currency_Code
DELIMITER '|' QUOTE '"'
)
In the above example, if middle name is blank, then it should still show one empty column with "|" delimiter as shown below.
Steigner|Debbie||USD
But it returns output as excluding middle name since it is blank.
Steigner|Debbie|USD
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4191) Add a NOQUOTE option for the TEXTAGG function
by Debbie Steigner (JIRA)
Debbie Steigner created TEIID-4191:
--------------------------------------
Summary: Add a NOQUOTE option for the TEXTAGG function
Key: TEIID-4191
URL: https://issues.jboss.org/browse/TEIID-4191
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 8.7.5.6_2
Reporter: Debbie Steigner
Assignee: Steven Hawkins
Currently on the TEXTAGG function it defaults to double quotes(") and you can specify something else with QUOTE, but there is not a way to have NO QUOTES at all. Can this be added?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4190) Enabling/Disabling a Datasource prompts for server restart
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIID-4190?page=com.atlassian.jira.plugin... ]
Steve Tran updated TEIID-4190:
------------------------------
Description:
When I enable or disable a Datasource in EAP (tested only in domain mode), I get a message that prompts me to restart my server because configurations have changed. This is a new warning because it didn't do this in earlier version of EAP6.4. If I go to the topology screen, none of the servers are marked with the symbol that says it needs to be restarted. If I drill down into the specific node and server, the Datasource was marked as disabled in the UI, so I think it did actually turned off the Datasource correctly.
I think the prompt is wrong, and should be removed. Also, this might be an EAP bug and not JDV related.
was:
Getting an error while replacing an existing VDB with JDV 6.2.4. I think the logging level is inappropriate since the VDB has full functionality since I am able to connect and execute some queries. Could lead to something more serious though, so reporting it as a bug until proven innocent.
{code}
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,954 WARN [org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already registered MBean: jgroups:type=protocol,cluster
="STEVE.1",protocol=UFCESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,955 WARN [org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already registered MBean: jgroups:type=protocol,cluster
="STEVE.1",protocol=GMSESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,957 WARN [org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already registered MBean: jgroups:type=protocol,cluster
="STEVE.1",protocol=STABLEESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,958 WARN [org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already registered MBean: jgroups:type=protocol,cluster
="STEVE.1",protocol=UNICAST2ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,959 WARN [org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already registered MBean: jgroups:type=protocol,cluster
="STEVE.1",protocol=NAKACKESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,961 WARN [org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already registered MBean: jgroups:type=protocol,cluster
="STEVE.1",protocol=BARRIERESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,961 WARN [org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already registered MBean: jgroups:type=protocol,cluster
="STEVE.1",protocol=VERIFY_SUSPECTESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,962 WARN [org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already registered MBean: jgroups:type=protocol,cluster
="STEVE.1",protocol=FDESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,963 WARN [org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already registered MBean: jgroups:type=protocol,cluster="STEVE.1",protocol=FD_SOCKESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,964 WARN [org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already registered MBean: jgroups:type=protocol,cluster="STEVE.1",protocol=MERGE2ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,964 WARN [org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already registered MBean: jgroups:type=protocol,cluster="STEVE.1",protocol=TCPPINGESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,965 WARN [org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already registered MBean: jgroups:type=protocol,cluster="STEVE.1",protocol=TCPESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,968 WARN [org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already registered MBean: jgroups:type=channel,cluster="STEVE.1"ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[31m22:08:39,969 ERROR [org.teiid.RUNTIME] (teiid-async-threads - 8) TEIID40088 Could not replicate object org.teiid.query.tempdata.GlobalTableStoreImpl@6518dd87: java.lang.IllegalStateException: cluster 'STEVE.1' is already connected to singleton transport: [dummy-1461636444525, dummy-1461636519952, PHX_ODS_DMM_LEGACY.1, PHX_ODS_DBA.1, Odata_TEST.1, ProjectionsUSHSI.1, ImputationV1.1, GMR_SQLDB_TEST.1, UK_PBS_VDB.1, EDE_US.1, BDF_CorrectionsVDB_V1.1, ImputationV1_DEV.1, HSISIT.1, UKPROJECTION.1, Gossip.1, HCR_CADM_CR_PROC.1, HSIWIP.1, MyVDB.1, dummy-1460722343623, HSIRES.1, KnowledgeFactory_Job.1, HSITEST.1, HCR_CADM_SYNDICATED.1, COL_VDB.1, dummy-1460722100133, $TEIID_BM$, BDF_CorrectionsVDB_SIT.1, dummy-1460720870935, PROJECTIONTEMPVDB.1, UK_PBS_Project_VDB.1, PROJECTIONVDB.1, $TEIID_ED$, DeployVDB.1, GMR_SQLDB_DBA.1, teiid-cache, STEVE.1, dummy-1460722176622, HCR_CADM.1, HSI.1, dummy-1461636277237, DedupsVdb.1, IMPUTATION_FRANCE.1, dummy-1460720872393, MSTRTestVdb.1]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:919) [jgroups-3.2.15.Final-redhat-1.jar:3.2.15.Final-redhat-1]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at org.jgroups.JChannel.startStack(JChannel.java:827) [jgroups-3.2.15.Final-redhat-1.jar:3.2.15.Final-redhat-1]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at org.jgroups.JChannel._preConnect(JChannel.java:525) [jgroups-3.2.15.Final-redhat-1.jar:3.2.15.Final-redhat-1]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at org.jgroups.JChannel.connect(JChannel.java:277) [jgroups-3.2.15.Final-redhat-1.jar:3.2.15.Final-redhat-1]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at org.jgroups.JChannel.connect(JChannel.java:268) [jgroups-3.2.15.Final-redhat-1.jar:3.2.15.Final-redhat-1]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at org.teiid.replication.jgroups.JGroupsObjectReplicator.replicate(JGroupsObjectReplicator.java:564) [teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at org.teiid.deployers.CompositeGlobalTableStore.createInstance(CompositeGlobalTableStore.java:57) [teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at org.teiid.jboss.VDBService$1.finishedDeployment(VDBService.java:156) [teiid-jboss-integration-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at org.teiid.deployers.VDBRepository.notifyFinished(VDBRepository.java:348) [teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at org.teiid.deployers.VDBRepository.finishDeployment(VDBRepository.java:304) [teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at org.teiid.runtime.AbstractVDBDeployer.metadataLoaded(AbstractVDBDeployer.java:202) [teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at org.teiid.jboss.VDBService.access$1100(VDBService.java:85) [teiid-jboss-integration-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at org.teiid.jboss.VDBService$6.run(VDBService.java:408) [teiid-jboss-integration-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at org.teiid.jboss.VDBService$7.run(VDBService.java:439) [teiid-jboss-integration-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_75]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]ESC[0m
{code}
> Enabling/Disabling a Datasource prompts for server restart
> ----------------------------------------------------------
>
> Key: TEIID-4190
> URL: https://issues.jboss.org/browse/TEIID-4190
> Project: Teiid
> Issue Type: Bug
> Environment: Red Hat JBoss Data Virtualization 6.2.4 on EAP patched to version 6.4.6, on Oracle Linux 6
> JBoss Developer Studio 8.1.0GA with Teiid Designer 9.0.6.Final-v20160316-1409-B1242 org.teiid.designer.feature.feature.group JBoss by Red Hat, Inc.
> 64-bit Windows 7 environment
> Reporter: Steve Tran
> Assignee: Steven Hawkins
> Attachments: Capture.PNG
>
>
> When I enable or disable a Datasource in EAP (tested only in domain mode), I get a message that prompts me to restart my server because configurations have changed. This is a new warning because it didn't do this in earlier version of EAP6.4. If I go to the topology screen, none of the servers are marked with the symbol that says it needs to be restarted. If I drill down into the specific node and server, the Datasource was marked as disabled in the UI, so I think it did actually turned off the Datasource correctly.
> I think the prompt is wrong, and should be removed. Also, this might be an EAP bug and not JDV related.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4190) Enabling/Disabling a Datasource prompts for server restart
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIID-4190?page=com.atlassian.jira.plugin... ]
Steve Tran updated TEIID-4190:
------------------------------
Attachment: Capture.PNG
> Enabling/Disabling a Datasource prompts for server restart
> ----------------------------------------------------------
>
> Key: TEIID-4190
> URL: https://issues.jboss.org/browse/TEIID-4190
> Project: Teiid
> Issue Type: Bug
> Environment: Red Hat JBoss Data Virtualization 6.2.4 on EAP patched to version 6.4.6, on Oracle Linux 6
> JBoss Developer Studio 8.1.0GA with Teiid Designer 9.0.6.Final-v20160316-1409-B1242 org.teiid.designer.feature.feature.group JBoss by Red Hat, Inc.
> 64-bit Windows 7 environment
> Reporter: Steve Tran
> Assignee: Steven Hawkins
> Attachments: Capture.PNG
>
>
> When I enable or disable a Datasource in EAP (tested only in domain mode), I get a message that prompts me to restart my server because configurations have changed. This is a new warning because it didn't do this in earlier version of EAP6.4. If I go to the topology screen, none of the servers are marked with the symbol that says it needs to be restarted. If I drill down into the specific node and server, the Datasource was marked as disabled in the UI, so I think it did actually turned off the Datasource correctly.
> I think the prompt is wrong, and should be removed. Also, this might be an EAP bug and not JDV related.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months