12:15 a.m.
Join between char and varchar
-----------------------------
Key: TEIID-1465
URL: https://issues.jboss.org/browse/TEIID-1465
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.3
Environment: Teiid 7.3 deployed on Jboss AS 5.1.0 GA running on Ubuntu Server
10.04 LTS, MySQL 5.1.51 running on the same machine as JBoss, SQL Server 2000 Standard SP4
running on Windows Server 2003
Reporter: Claudio Venturini
Assignee: Steven Hawkins
Joins between char and varchar fields fail.
Suppose to have a table T1 with a field A, declared as char(10), and a table T2 with a
field B, declared as varchar(10). Suppose that the two tables have the following data.
*T1*:
||A||
|ML0001|
*T2*:
||B||
|ML0001|
When performing a INNER JOIN with the condition {{T1.A = T2.B}} the result set is empty,
even if the two record match correctly.
This happens when the two base tables refer to two different sources, because if they are
in the same source Teiid pushes the join to the source, which computes it correctly.
I think the problem is in the comparison of the two strings. I have the table T1 in SQL
Server 2000, and the table T2 in MySQL 5.1.
If one asks SQL Server to convert the string to bytes, the result is
{{0x4D4C3030303120202020}}, because the string is filled with (invisible) blanks in order
to reach the limit of 10 characters. Note that if one asks for the length of that string,
SQL Server states (correctly) that it is 6 characters.
The string in MySQL is a VARCHAR(10), so its conversion to binary is {{0x4D4C30303031}}.
I think that Teiid compares the two binary strings in their entire length. That comparison
fails, and no match is found.
The problem remains even if the table T1 is placed in MySQL, and T2 in SQL Server (the
opposite situation). I also verified that the problem exists either when querying the
source models or view models built over them.
*Workaround:*
A workaround exists but it is too complex (IMHO). I haven't tested it with many
records, but I think it will slow down performances considerably.
It consists in casting the string from char to varchar, and then trimming it (with RTRIM()
and LTRIM() because SQL Server doesn't support TRIM()). So the join condition is:
{noformat}
RTRIM(LTRIM(CAST(T1.A AS VARCHAR))) = T2.B
{noformat}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:09 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1465) Join between char and varchar
[
https://issues.jboss.org/browse/TEIID-1465?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1465:
---------------------------------------
Teiid is comparing the string form as returned by the JDBC driver. char values retrieved
this way generally do append spaces. The Teiid string comparison then treats all
characters as meaningful, which fails your equality check. There is a built-in workaround
for this situation in Teiid, which is the trimstrings setting on any JDBC translator.
trimstrings is a little heavy handed though. Any column reference to a char type in the
source sql will be wrapped in the source's equivalent of rtrim. So you're
workaround that is targeted to just your join condition may be more appropriate.
Teiid would need to add a true char type to support comparison and other methods that
ignores padding.
Join between char and varchar
-----------------------------
Key: TEIID-1465
URL: https://issues.jboss.org/browse/TEIID-1465
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.3
Environment: Teiid 7.3 deployed on Jboss AS 5.1.0 GA running on Ubuntu Server
10.04 LTS, MySQL 5.1.51 running on the same machine as JBoss, SQL Server 2000 Standard SP4
running on Windows Server 2003
Reporter: Claudio Venturini
Assignee: Steven Hawkins
Labels: char, join, varchar
Joins between char and varchar fields fail.
Suppose to have a table T1 with a field A, declared as char(10), and a table T2 with a
field B, declared as varchar(10). Suppose that the two tables have the following data.
*T1*:
||A||
|ML0001|
*T2*:
||B||
|ML0001|
When performing a INNER JOIN with the condition {{T1.A = T2.B}} the result set is empty,
even if the two record match correctly.
This happens when the two base tables refer to two different sources, because if they are
in the same source Teiid pushes the join to the source, which computes it correctly.
I think the problem is in the comparison of the two strings. I have the table T1 in SQL
Server 2000, and the table T2 in MySQL 5.1.
If one asks SQL Server to convert the string to bytes, the result is
{{0x4D4C3030303120202020}}, because the string is filled with (invisible) blanks in order
to reach the limit of 10 characters. Note that if one asks for the length of that string,
SQL Server states (correctly) that it is 6 characters.
The string in MySQL is a VARCHAR(10), so its conversion to binary is {{0x4D4C30303031}}.
I think that Teiid compares the two binary strings in their entire length. That
comparison fails, and no match is found.
The problem remains even if the table T1 is placed in MySQL, and T2 in SQL Server (the
opposite situation). I also verified that the problem exists either when querying the
source models or view models built over them.
*Workaround:*
A workaround exists but it is too complex (IMHO). I haven't tested it with many
records, but I think it will slow down performances considerably.
It consists in casting the string from char to varchar, and then trimming it (with
RTRIM() and LTRIM() because SQL Server doesn't support TRIM()). So the join condition
is:
{noformat}
RTRIM(LTRIM(CAST(T1.A AS VARCHAR))) = T2.B
{noformat}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:28 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1465) Join between char and varchar
[
https://issues.jboss.org/browse/TEIID-1465?page=com.atlassian.jira.plugin...
]
Claudio Venturini commented on TEIID-1465:
------------------------------------------
Thanks Steven, for now I will use my workaround. I didn't know about the trimstring
setting. Anyway, is in the Teiid plan the fix for this issue?
Join between char and varchar
-----------------------------
Key: TEIID-1465
URL: https://issues.jboss.org/browse/TEIID-1465
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.3
Environment: Teiid 7.3 deployed on Jboss AS 5.1.0 GA running on Ubuntu Server
10.04 LTS, MySQL 5.1.51 running on the same machine as JBoss, SQL Server 2000 Standard SP4
running on Windows Server 2003
Reporter: Claudio Venturini
Assignee: Steven Hawkins
Labels: char, join, varchar
Joins between char and varchar fields fail.
Suppose to have a table T1 with a field A, declared as char(10), and a table T2 with a
field B, declared as varchar(10). Suppose that the two tables have the following data.
*T1*:
||A||
|ML0001|
*T2*:
||B||
|ML0001|
When performing a INNER JOIN with the condition {{T1.A = T2.B}} the result set is empty,
even if the two record match correctly.
This happens when the two base tables refer to two different sources, because if they are
in the same source Teiid pushes the join to the source, which computes it correctly.
I think the problem is in the comparison of the two strings. I have the table T1 in SQL
Server 2000, and the table T2 in MySQL 5.1.
If one asks SQL Server to convert the string to bytes, the result is
{{0x4D4C3030303120202020}}, because the string is filled with (invisible) blanks in order
to reach the limit of 10 characters. Note that if one asks for the length of that string,
SQL Server states (correctly) that it is 6 characters.
The string in MySQL is a VARCHAR(10), so its conversion to binary is {{0x4D4C30303031}}.
I think that Teiid compares the two binary strings in their entire length. That
comparison fails, and no match is found.
The problem remains even if the table T1 is placed in MySQL, and T2 in SQL Server (the
opposite situation). I also verified that the problem exists either when querying the
source models or view models built over them.
*Workaround:*
A workaround exists but it is too complex (IMHO). I haven't tested it with many
records, but I think it will slow down performances considerably.
It consists in casting the string from char to varchar, and then trimming it (with
RTRIM() and LTRIM() because SQL Server doesn't support TRIM()). So the join condition
is:
{noformat}
RTRIM(LTRIM(CAST(T1.A AS VARCHAR))) = T2.B
{noformat}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:47 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-1465) Join between char and varchar
[
https://issues.jboss.org/browse/TEIID-1465?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1465:
---------------------------------------
I don't think that we'll introduce a proper char type until Teiid 9. Until then
manually adding a trim/rtrim function in your teiid sql or using the trimstrings setting
would be the suggested workaround.
Join between char and varchar
-----------------------------
Key: TEIID-1465
URL: https://issues.jboss.org/browse/TEIID-1465
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.3
Environment: Teiid 7.3 deployed on Jboss AS 5.1.0 GA running on Ubuntu Server
10.04 LTS, MySQL 5.1.51 running on the same machine as JBoss, SQL Server 2000 Standard SP4
running on Windows Server 2003
Reporter: Claudio Venturini
Assignee: Steven Hawkins
Labels: char, join, varchar
Joins between char and varchar fields fail.
Suppose to have a table T1 with a field A, declared as char(10), and a table T2 with a
field B, declared as varchar(10). Suppose that the two tables have the following data.
*T1*:
||A||
|ML0001|
*T2*:
||B||
|ML0001|
When performing a INNER JOIN with the condition {{T1.A = T2.B}} the result set is empty,
even if the two record match correctly.
This happens when the two base tables refer to two different sources, because if they are
in the same source Teiid pushes the join to the source, which computes it correctly.
I think the problem is in the comparison of the two strings. I have the table T1 in SQL
Server 2000, and the table T2 in MySQL 5.1.
If one asks SQL Server to convert the string to bytes, the result is
{{0x4D4C3030303120202020}}, because the string is filled with (invisible) blanks in order
to reach the limit of 10 characters. Note that if one asks for the length of that string,
SQL Server states (correctly) that it is 6 characters.
The string in MySQL is a VARCHAR(10), so its conversion to binary is {{0x4D4C30303031}}.
I think that Teiid compares the two binary strings in their entire length. That
comparison fails, and no match is found.
The problem remains even if the table T1 is placed in MySQL, and T2 in SQL Server (the
opposite situation). I also verified that the problem exists either when querying the
source models or view models built over them.
*Workaround:*
A workaround exists but it is too complex (IMHO). I haven't tested it with many
records, but I think it will slow down performances considerably.
It consists in casting the string from char to varchar, and then trimming it (with
RTRIM() and LTRIM() because SQL Server doesn't support TRIM()). So the join condition
is:
{noformat}
RTRIM(LTRIM(CAST(T1.A AS VARCHAR))) = T2.B
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:52 p.m.
New subject: [JBoss JIRA] Resolved: (TEIID-1465) Join between char and varchar
[
https://issues.jboss.org/browse/TEIID-1465?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1465.
-----------------------------------
Resolution: Deferred
Marking as deferred. We should consider adding char/byte types in Teiid 9.0.
The workarounds for non-single character char types are currently:
1. use the jdbc translator trim strings setting
2. use a targeted trim for equality comparisons, e.g.
rtrim(charCol) = vcharCol
3. introduce a source view that performs the conversion of the fixed char column to
varchar
Join between char and varchar
-----------------------------
Key: TEIID-1465
URL: https://issues.jboss.org/browse/TEIID-1465
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.3
Environment: Teiid 7.3 deployed on Jboss AS 5.1.0 GA running on Ubuntu Server
10.04 LTS, MySQL 5.1.51 running on the same machine as JBoss, SQL Server 2000 Standard SP4
running on Windows Server 2003
Reporter: Claudio Venturini
Assignee: Steven Hawkins
Labels: char, join, varchar
Joins between char and varchar fields fail.
Suppose to have a table T1 with a field A, declared as char(10), and a table T2 with a
field B, declared as varchar(10). Suppose that the two tables have the following data.
*T1*:
||A||
|ML0001|
*T2*:
||B||
|ML0001|
When performing a INNER JOIN with the condition {{T1.A = T2.B}} the result set is empty,
even if the two record match correctly.
This happens when the two base tables refer to two different sources, because if they are
in the same source Teiid pushes the join to the source, which computes it correctly.
I think the problem is in the comparison of the two strings. I have the table T1 in SQL
Server 2000, and the table T2 in MySQL 5.1.
If one asks SQL Server to convert the string to bytes, the result is
{{0x4D4C3030303120202020}}, because the string is filled with (invisible) blanks in order
to reach the limit of 10 characters. Note that if one asks for the length of that string,
SQL Server states (correctly) that it is 6 characters.
The string in MySQL is a VARCHAR(10), so its conversion to binary is {{0x4D4C30303031}}.
I think that Teiid compares the two binary strings in their entire length. That
comparison fails, and no match is found.
The problem remains even if the table T1 is placed in MySQL, and T2 in SQL Server (the
opposite situation). I also verified that the problem exists either when querying the
source models or view models built over them.
*Workaround:*
A workaround exists but it is too complex (IMHO). I haven't tested it with many
records, but I think it will slow down performances considerably.
It consists in casting the string from char to varchar, and then trimming it (with
RTRIM() and LTRIM() because SQL Server doesn't support TRIM()). So the join condition
is:
{noformat}
RTRIM(LTRIM(CAST(T1.A AS VARCHAR))) = T2.B
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:37 p.m.
New subject: [JBoss JIRA] (TEIID-1465) Join between char and varchar
[
https://issues.jboss.org/browse/TEIID-1465?page=com.atlassian.jira.plugin...
]
Steven Hawkins reopened TEIID-1465:
-----------------------------------
Reopening to add a system switch for padded comparison.
Join between char and varchar
-----------------------------
Key: TEIID-1465
URL: https://issues.jboss.org/browse/TEIID-1465
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.3
Environment: Teiid 7.3 deployed on Jboss AS 5.1.0 GA running on Ubuntu Server
10.04 LTS, MySQL 5.1.51 running on the same machine as JBoss, SQL Server 2000 Standard SP4
running on Windows Server 2003
Reporter: Claudio Venturini
Assignee: Steven Hawkins
Labels: char, join, varchar
Joins between char and varchar fields fail.
Suppose to have a table T1 with a field A, declared as char(10), and a table T2 with a
field B, declared as varchar(10). Suppose that the two tables have the following data.
*T1*:
||A||
|ML0001|
*T2*:
||B||
|ML0001|
When performing a INNER JOIN with the condition {{T1.A = T2.B}} the result set is empty,
even if the two record match correctly.
This happens when the two base tables refer to two different sources, because if they are
in the same source Teiid pushes the join to the source, which computes it correctly.
I think the problem is in the comparison of the two strings. I have the table T1 in SQL
Server 2000, and the table T2 in MySQL 5.1.
If one asks SQL Server to convert the string to bytes, the result is
{{0x4D4C3030303120202020}}, because the string is filled with (invisible) blanks in order
to reach the limit of 10 characters. Note that if one asks for the length of that string,
SQL Server states (correctly) that it is 6 characters.
The string in MySQL is a VARCHAR(10), so its conversion to binary is {{0x4D4C30303031}}.
I think that Teiid compares the two binary strings in their entire length. That
comparison fails, and no match is found.
The problem remains even if the table T1 is placed in MySQL, and T2 in SQL Server (the
opposite situation). I also verified that the problem exists either when querying the
source models or view models built over them.
*Workaround:*
A workaround exists but it is too complex (IMHO). I haven't tested it with many
records, but I think it will slow down performances considerably.
It consists in casting the string from char to varchar, and then trimming it (with
RTRIM() and LTRIM() because SQL Server doesn't support TRIM()). So the join condition
is:
{noformat}
RTRIM(LTRIM(CAST(T1.A AS VARCHAR))) = T2.B
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:14 a.m.
New subject: [JBoss JIRA] (TEIID-1465) Join between char and varchar
[
https://issues.jboss.org/browse/TEIID-1465?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-1465:
----------------------------------
Fix Version/s: 8.0
Workaround Description: Use the trimstrings option for jdbc sources returning char
values.
Workaround: Workaround Exists
Join between char and varchar
-----------------------------
Key: TEIID-1465
URL: https://issues.jboss.org/browse/TEIID-1465
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.3
Environment: Teiid 7.3 deployed on Jboss AS 5.1.0 GA running on Ubuntu Server
10.04 LTS, MySQL 5.1.51 running on the same machine as JBoss, SQL Server 2000 Standard SP4
running on Windows Server 2003
Reporter: Claudio Venturini
Assignee: Steven Hawkins
Labels: char, join, varchar
Fix For: 8.0
Joins between char and varchar fields fail.
Suppose to have a table T1 with a field A, declared as char(10), and a table T2 with a
field B, declared as varchar(10). Suppose that the two tables have the following data.
*T1*:
||A||
|ML0001|
*T2*:
||B||
|ML0001|
When performing a INNER JOIN with the condition {{T1.A = T2.B}} the result set is empty,
even if the two record match correctly.
This happens when the two base tables refer to two different sources, because if they are
in the same source Teiid pushes the join to the source, which computes it correctly.
I think the problem is in the comparison of the two strings. I have the table T1 in SQL
Server 2000, and the table T2 in MySQL 5.1.
If one asks SQL Server to convert the string to bytes, the result is
{{0x4D4C3030303120202020}}, because the string is filled with (invisible) blanks in order
to reach the limit of 10 characters. Note that if one asks for the length of that string,
SQL Server states (correctly) that it is 6 characters.
The string in MySQL is a VARCHAR(10), so its conversion to binary is {{0x4D4C30303031}}.
I think that Teiid compares the two binary strings in their entire length. That
comparison fails, and no match is found.
The problem remains even if the table T1 is placed in MySQL, and T2 in SQL Server (the
opposite situation). I also verified that the problem exists either when querying the
source models or view models built over them.
*Workaround:*
A workaround exists but it is too complex (IMHO). I haven't tested it with many
records, but I think it will slow down performances considerably.
It consists in casting the string from char to varchar, and then trimming it (with
RTRIM() and LTRIM() because SQL Server doesn't support TRIM()). So the join condition
is:
{noformat}
RTRIM(LTRIM(CAST(T1.A AS VARCHAR))) = T2.B
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:25 a.m.
New subject: [JBoss JIRA] (TEIID-1465) Join between char and varchar
[
https://issues.jboss.org/browse/TEIID-1465?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1465.
-----------------------------------
Resolution: Partially Completed
Added the org.teiid.padSpace boolean system property to compare strings as if they are
effectively right padded. However there is still no true char type or ability to change
other collation attributes.
Join between char and varchar
-----------------------------
Key: TEIID-1465
URL: https://issues.jboss.org/browse/TEIID-1465
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.3
Environment: Teiid 7.3 deployed on Jboss AS 5.1.0 GA running on Ubuntu Server
10.04 LTS, MySQL 5.1.51 running on the same machine as JBoss, SQL Server 2000 Standard SP4
running on Windows Server 2003
Reporter: Claudio Venturini
Assignee: Steven Hawkins
Labels: char, join, varchar
Fix For: 8.0
Joins between char and varchar fields fail.
Suppose to have a table T1 with a field A, declared as char(10), and a table T2 with a
field B, declared as varchar(10). Suppose that the two tables have the following data.
*T1*:
||A||
|ML0001|
*T2*:
||B||
|ML0001|
When performing a INNER JOIN with the condition {{T1.A = T2.B}} the result set is empty,
even if the two record match correctly.
This happens when the two base tables refer to two different sources, because if they are
in the same source Teiid pushes the join to the source, which computes it correctly.
I think the problem is in the comparison of the two strings. I have the table T1 in SQL
Server 2000, and the table T2 in MySQL 5.1.
If one asks SQL Server to convert the string to bytes, the result is
{{0x4D4C3030303120202020}}, because the string is filled with (invisible) blanks in order
to reach the limit of 10 characters. Note that if one asks for the length of that string,
SQL Server states (correctly) that it is 6 characters.
The string in MySQL is a VARCHAR(10), so its conversion to binary is {{0x4D4C30303031}}.
I think that Teiid compares the two binary strings in their entire length. That
comparison fails, and no match is found.
The problem remains even if the table T1 is placed in MySQL, and T2 in SQL Server (the
opposite situation). I also verified that the problem exists either when querying the
source models or view models built over them.
*Workaround:*
A workaround exists but it is too complex (IMHO). I haven't tested it with many
records, but I think it will slow down performances considerably.
It consists in casting the string from char to varchar, and then trimming it (with
RTRIM() and LTRIM() because SQL Server doesn't support TRIM()). So the join condition
is:
{noformat}
RTRIM(LTRIM(CAST(T1.A AS VARCHAR))) = T2.B
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:15 p.m.
New subject: [JBoss JIRA] (TEIID-1465) Join between char and varchar
[
https://issues.jboss.org/browse/TEIID-1465?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-1465:
----------------------------------
Fix Version/s: 7.7
Join between char and varchar
-----------------------------
Key: TEIID-1465
URL: https://issues.jboss.org/browse/TEIID-1465
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.3
Environment: Teiid 7.3 deployed on Jboss AS 5.1.0 GA running on Ubuntu Server
10.04 LTS, MySQL 5.1.51 running on the same machine as JBoss, SQL Server 2000 Standard SP4
running on Windows Server 2003
Reporter: Claudio Venturini
Assignee: Steven Hawkins
Labels: char, join, varchar
Fix For: 7.7, 8.0
Joins between char and varchar fields fail.
Suppose to have a table T1 with a field A, declared as char(10), and a table T2 with a
field B, declared as varchar(10). Suppose that the two tables have the following data.
*T1*:
||A||
|ML0001|
*T2*:
||B||
|ML0001|
When performing a INNER JOIN with the condition {{T1.A = T2.B}} the result set is empty,
even if the two record match correctly.
This happens when the two base tables refer to two different sources, because if they are
in the same source Teiid pushes the join to the source, which computes it correctly.
I think the problem is in the comparison of the two strings. I have the table T1 in SQL
Server 2000, and the table T2 in MySQL 5.1.
If one asks SQL Server to convert the string to bytes, the result is
{{0x4D4C3030303120202020}}, because the string is filled with (invisible) blanks in order
to reach the limit of 10 characters. Note that if one asks for the length of that string,
SQL Server states (correctly) that it is 6 characters.
The string in MySQL is a VARCHAR(10), so its conversion to binary is {{0x4D4C30303031}}.
I think that Teiid compares the two binary strings in their entire length. That
comparison fails, and no match is found.
The problem remains even if the table T1 is placed in MySQL, and T2 in SQL Server (the
opposite situation). I also verified that the problem exists either when querying the
source models or view models built over them.
*Workaround:*
A workaround exists but it is too complex (IMHO). I haven't tested it with many
records, but I think it will slow down performances considerably.
It consists in casting the string from char to varchar, and then trimming it (with
RTRIM() and LTRIM() because SQL Server doesn't support TRIM()). So the join condition
is:
{noformat}
RTRIM(LTRIM(CAST(T1.A AS VARCHAR))) = T2.B
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4501
days inactive
4882
days old
8 comments
2 participants
participants (2)
-
Claudio Venturini (JIRA) -
Steven Hawkins (JIRA)