[
https://issues.apache.org/jira/browse/PHOENIX-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485719#comment-14485719
]
Nick Dimiduk commented on PHOENIX-1824:
---------------------------------------
bq. Are you thinking we will want to run all the ITs both ways - with the query
server and standard client?
Yes, for confidence in our query server, we'll want confidence that all phoenix
features work through it. Thus I think it makes sense that we have an easy way
to run all IT's through both drivers. In theory, they query server will
eventually have a larger user audience than the Java driver, so confidence will
become very important.
bq. How would the @Parameterzied annotation work cleanly?
That I'm not sure about yet. I think a common base class for all IT's that sets
up the parameters and listens to the harness for instructions to run only one
way or the other. I think the common base class will create less burden on
developers in the future including coverage for both runtime environments.
Perhaps you know junit better than I, so I'll defer to your recommendation.
> Run all IT's through Query Server
> ---------------------------------
>
> Key: PHOENIX-1824
> URL: https://issues.apache.org/jira/browse/PHOENIX-1824
> Project: Phoenix
> Issue Type: Test
> Affects Versions: 4.4.0
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Attachments: 1824.wip.patch
>
>
> Once we have PHOENIX-971 merged, we can increase our confidence in the server
> by parameterizing our IT suite to run over either driver, or both. This will
> probably require refactoring the IT suite out of phoenix-core/src/it into a
> separate module so that module can depend on both phoenix-core and
> phoenix-server modules.
> This is looking like it will also depend on improvements to Calcite that may
> not make it into 1.2 release (as RC's for that release have already started).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
