[JBoss JIRA] (TEIID-3149) External materialization management with Embedded Server
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3149?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3149:
----------------------------------
Summary: External materialization management with Embedded Server (was: External materialization with Embedded Server)
Description: External materialization management is currently only enabled for the AS server environment.
Labels: External materialization (was: Embedded External Server materialization with)
Assignee: (was: Steven Hawkins)
Component/s: Embedded
> External materialization management with Embedded Server
> --------------------------------------------------------
>
> Key: TEIID-3149
> URL: https://issues.jboss.org/browse/TEIID-3149
> Project: Teiid
> Issue Type: Enhancement
> Components: Embedded
> Reporter: Joseph CHIDIAC
> Labels: External, materialization
>
> External materialization management is currently only enabled for the AS server environment.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (TEIID-3145) GroovyCastException when starting adminshell
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3145?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3145:
----------------------------------
Assignee: Van Halbert (was: Steven Hawkins)
Assigning to Van to determine which direction to go with the groovy-all dependency.
> GroovyCastException when starting adminshell
> --------------------------------------------
>
> Key: TEIID-3145
> URL: https://issues.jboss.org/browse/TEIID-3145
> Project: Teiid
> Issue Type: Bug
> Components: Tools
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Van Halbert
>
> When I run adminshell.sh, admishell will throw following exception:
> Exception in thread "main" org.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object 'org.codehaus.groovy.tools.shell.util.HelpFormatter@3004baef' with class 'org.codehaus.groovy.tools.shell.util.HelpFormatter' to class 'org.apache.commons.cli.HelpFormatter'
> at org.codehaus.groovy.runtime.typehandling.DefaultTypeTransformation.castToType(DefaultTypeTransformation.java:360)
> at groovy.lang.MetaClassImpl.setProperty(MetaClassImpl.java:2394)
> at groovy.lang.MetaClassImpl.setProperty(MetaClassImpl.java:3335)
> at groovy.lang.MetaClassImpl.setProperties(MetaClassImpl.java:1497)
> at org.codehaus.groovy.runtime.callsite.ConstructorSite$NoParamSite.callConstructor(ConstructorSite.java:122)
> at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:57)
> at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:182)
> at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:190)
> at org.codehaus.groovy.tools.shell.Main.main(Main.groovy:50)
> at org.teiid.adminshell.GroovyAdminShell.main(GroovyAdminShell.java:30)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (TEIID-3146) Billing mechanism based on the query's complexity
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3146?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3146:
---------------------------------------
I'm not sure we can provide a turn-key billing mechanism. It's best to concentrate on the underlying parameters and work from there. We have
TEIID-3146 - for bytes transferred to the Teiid client
The various processing time in the query plan and TEIID-2813 which is applicable to processor threads (although they end up doing some processing work on behalf of other threads in the buffer manager) as well to get the cpu time rather than the wall clock time.
We could also look at adding memory batch statistics to the plan - however that can get messy as typically you'd want to correlate to disk usage which is handled lower down and by other threads etc.
> Billing mechanism based on the query's complexity
> -------------------------------------------------
>
> Key: TEIID-3146
> URL: https://issues.jboss.org/browse/TEIID-3146
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Joao Viragine
> Assignee: Steven Hawkins
> Priority: Minor
>
> It would be nice if we had a billing mechanism based on the query's complexity.
> Teeid exposes information about the queries issued, the amount of records returned, the time elapsed and the query plan.
> It could also expose the amount of data (in bytes) returned by each query.
> We could combine the above data plus the query complexity to create a score for a billing calculation.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (TEIID-3147) Add information about the amount of data (in bytes) returned by each query
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3147?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3147:
---------------------------------------
The ObjectEncoder at the transport level knows about the size of messages written - but doesn't correlate that with a particular session/query. It also will not differentiate between the message bytes and the data bytes (although things like source warnings fall somewhere in between). Correlating back to something like command log would be especially messy here as we would have to know the intent of the messages (query results vs response to transactional control operations, ping, etc.).
Alternatively this could be handled as a feature in itself where we pre-serialize the data (again with special considerations towards things like source warnings ) and report it in the engine.
> Add information about the amount of data (in bytes) returned by each query
> --------------------------------------------------------------------------
>
> Key: TEIID-3147
> URL: https://issues.jboss.org/browse/TEIID-3147
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Joao Viragine
> Assignee: Steven Hawkins
>
> It would be nice if we had the information about the amount of data (in bytes) returned by each query.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (TEIID-3148) Teiid exception with vdb from flat file containing utf8 non-ascii character
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3148?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3148:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1147508|https://bugzilla.redhat.com/show_bug.cgi?id=1147508] from NEW to CLOSED
> Teiid exception with vdb from flat file containing utf8 non-ascii character
> ---------------------------------------------------------------------------
>
> Key: TEIID-3148
> URL: https://issues.jboss.org/browse/TEIID-3148
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1
> Environment: Windows OS
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
>
> This issue is Windows OS specific. When trying to parse text csv file in utf8 which contains non-ascii characters an exception occurs. When the non-ascii characters are removed, everything passes well. On RHEL or Solaris this issue doesn't occur.
> TEIID30020 Processing exception for request rgzZ3dn9tVMX.0 'TEIID30179 Text parse error: Could not read data in file:/w:/workspace/JDV6_1_BQT-jstastny/jdk/java17_default/label/Win2k8_x86/eap/standalone/deployments/TextEmployeeTest-files/EmpData.txt'. Originally TeiidProcessingException 'Input length = 1' CoderResult.java:278.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (TEIID-3148) Teiid exception with vdb from flat file containing utf8 non-ascii character
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3148?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3148.
-----------------------------------
Resolution: Rejected
In addition to setting the encoding for all getTextFile calls you can also just use getFile to obtain a blob and use the to_chars function to specify the character set.
> Teiid exception with vdb from flat file containing utf8 non-ascii character
> ---------------------------------------------------------------------------
>
> Key: TEIID-3148
> URL: https://issues.jboss.org/browse/TEIID-3148
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1
> Environment: Windows OS
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
>
> This issue is Windows OS specific. When trying to parse text csv file in utf8 which contains non-ascii characters an exception occurs. When the non-ascii characters are removed, everything passes well. On RHEL or Solaris this issue doesn't occur.
> TEIID30020 Processing exception for request rgzZ3dn9tVMX.0 'TEIID30179 Text parse error: Could not read data in file:/w:/workspace/JDV6_1_BQT-jstastny/jdk/java17_default/label/Win2k8_x86/eap/standalone/deployments/TextEmployeeTest-files/EmpData.txt'. Originally TeiidProcessingException 'Input length = 1' CoderResult.java:278.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (TEIID-3148) Teiid exception with vdb from flat file containing utf8 non-ascii character
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-3148?page=com.atlassian.jira.plugin... ]
Jan Stastny commented on TEIID-3148:
------------------------------------
I have set Encoding property to 'utf8' via TeiidDesigner and everything works as expected.
Thanks Steven.
> Teiid exception with vdb from flat file containing utf8 non-ascii character
> ---------------------------------------------------------------------------
>
> Key: TEIID-3148
> URL: https://issues.jboss.org/browse/TEIID-3148
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1
> Environment: Windows OS
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
>
> This issue is Windows OS specific. When trying to parse text csv file in utf8 which contains non-ascii characters an exception occurs. When the non-ascii characters are removed, everything passes well. On RHEL or Solaris this issue doesn't occur.
> TEIID30020 Processing exception for request rgzZ3dn9tVMX.0 'TEIID30179 Text parse error: Could not read data in file:/w:/workspace/JDV6_1_BQT-jstastny/jdk/java17_default/label/Win2k8_x86/eap/standalone/deployments/TextEmployeeTest-files/EmpData.txt'. Originally TeiidProcessingException 'Input length = 1' CoderResult.java:278.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (TEIID-3148) Teiid exception with vdb from flat file containing utf8 non-ascii character
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3148?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3148:
---------------------------------------
Do you have an encoding set on the file translator? If not it will default to the system default for your JVM.
> Teiid exception with vdb from flat file containing utf8 non-ascii character
> ---------------------------------------------------------------------------
>
> Key: TEIID-3148
> URL: https://issues.jboss.org/browse/TEIID-3148
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1
> Environment: Windows OS
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
>
> This issue is Windows OS specific. When trying to parse text csv file in utf8 which contains non-ascii characters an exception occurs. When the non-ascii characters are removed, everything passes well. On RHEL or Solaris this issue doesn't occur.
> TEIID30020 Processing exception for request rgzZ3dn9tVMX.0 'TEIID30179 Text parse error: Could not read data in file:/w:/workspace/JDV6_1_BQT-jstastny/jdk/java17_default/label/Win2k8_x86/eap/standalone/deployments/TextEmployeeTest-files/EmpData.txt'. Originally TeiidProcessingException 'Input length = 1' CoderResult.java:278.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months