[jira] [Comment Edited] (HADOOP-13966) add ability to start DDB local server in every test
[
https://issues.apache.org/jira/browse/HADOOP-13966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15934842#comment-15934842
]
Steve Loughran edited comment on HADOOP-13966 at 3/21/17 4:41 PM:
--
# don't worry about the logout, JVM termination will do that
# do skip setting the sql lite sysprop if already set
# we need to make sure that the sqllist property is unique for multiple JVMs
running in parallel. That could be done by using the system property
test.build.data , which is customised in the maven parallel test runner,
falling back to "target" if unset.
# {{startSingletonServer}} to throw exceptions
# oh, and use the OS specific "/" path separator character
# maybe mention in test docs "how to keep costs down"
was (Author: ste...@apache.org):
# don't worry about the logout, JVM termination will do that
# do skip setting the sql lite sysprop if already set
# we need to make sure that the sqllist property is unique for multiple JVMs
running in parallel. That could be done by using the system property
test.build.data , which is customised in the maven parallel test runner,
falling back to "target" if unset.
# {{startSingletonServer}} to throw exceptions
# oh, and use the OS specific "/" path separator character
> add ability to start DDB local server in every test
> ---
>
> Key: HADOOP-13966
> URL: https://issues.apache.org/jira/browse/HADOOP-13966
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: test
>Affects Versions: HADOOP-13345
>Reporter: Steve Loughran
> Attachments: HADOOP-13966-HADOOP-13345.000.patch
>
>
> the local in memory DDB starts up in only 2+ seconds, so we have to reason to
> not use it in all our integration tests, if we add a switch to do this
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (HADOOP-13966) add ability to start DDB local server in every test
[
https://issues.apache.org/jira/browse/HADOOP-13966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15934842#comment-15934842
]
Steve Loughran edited comment on HADOOP-13966 at 3/21/17 4:34 PM:
--
# don't worry about the logout, JVM termination will do that
# do skip setting the sql lite sysprop if already set
# we need to make sure that the sqllist property is unique for multiple JVMs
running in parallel. That could be done by using the system property
test.build.data , which is customised in the maven parallel test runner,
falling back to "target" if unset.
# {{startSingletonServer}} to throw exceptions
# oh, and use the OS specific "/" path separator character
was (Author: ste...@apache.org):
# don't worry about the logout, JVM termination will do that
# do skip setting the sql lite sysprop if already set
# we need to make sure that the sqllist property is unique for multiple JVMs
running in parallel. That could be done by using the system property
test.build.data , which is customised in the maven parallel test runner,
falling back to "target" if unset.
# oh, and use the OS specific "/" path separator character
> add ability to start DDB local server in every test
> ---
>
> Key: HADOOP-13966
> URL: https://issues.apache.org/jira/browse/HADOOP-13966
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: test
>Affects Versions: HADOOP-13345
>Reporter: Steve Loughran
> Attachments: HADOOP-13966-HADOOP-13345.000.patch
>
>
> the local in memory DDB starts up in only 2+ seconds, so we have to reason to
> not use it in all our integration tests, if we add a switch to do this
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
