[
https://issues.apache.org/jira/browse/DERBY-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662514#action_12662514
]
Rick Hillegas commented on DERBY-4014:
--------------------------------------
Hi Kathey. Looks good to me. I applied the patch and then ran the
demoFileVtis.sql script. One thing I noticed is that the fixVersion elements
are all concatenated, so the sample row that is selected by the
apacheVanillaReport vti has a fixVersion field which looks like this:
"10.2.2.110.3.1.410.4.0.0". You might want to think about how you want to
handle that. Here are two suggestions:
1) Write a wrapper function that reformats that field for you. So you would
write a query something like this:
select myFormatter( s."fixVersion" )
from table( "apacheVanillaLogFile"(
'file:///opt/DerbyTrunk/java/demo/vtis/data/ApacheServerLog.xml' ) ) s
2) You could also change XmlVTI.parseRow() to do something other than just
concatenate identically named child elements. E.g., insert a space between the
text contents of those children.
> Update Derby Jira Report XML VTI to access more fields
> ------------------------------------------------------
>
> Key: DERBY-4014
> URL: https://issues.apache.org/jira/browse/DERBY-4014
> Project: Derby
> Issue Type: Improvement
> Components: Demos/Scripts
> Affects Versions: 10.5.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: derby-4014_diff.txt
>
>
> It would be useful for backporting reports and other Jira analysis reports to
> have the apacheVanillaReport access more of the item fields. Some missing
> are assignee, version, fix version, resolution,
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
