udaykiran19491/user-stories-from-tawos-for-llm-fine-tuning huggingface dataset:
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: hdfsjdbc throws an exception: {code} org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 'itemReader' defined in URL [file:/Users/trisberg/Projects/spring-xd/build/dist/spring-xd/xd/modules/job/hdfsjdbc/config/hdfsjdbc.xml]: Could not resolve placeholder 'columns' in string value "${columns}" {code}  The hdfsjdbc job uses 'columns' instead of 'names' as the parameter for the column-names. Should we make this usage consistent between jobs?  There is a comment in the docs - "there is also a limitation in that the database table must be created manually. This is due to a bug in Spring Hadoop and will be fixed in the future." Think this is this solved in Spring Hadoop now?  initializeDatabase should default to false now to be consistent with jdbc sink  Rename batch-jdbc/mongo-import.properties to batch-jdbc/mongo.properties since these aren't just for import
Answer: 2681.0

User story: "filejdbc throws an exception:  {code} java.lang.IllegalArgumentException: Could not resolve resource location pattern [/mycsvdir/*.csv]: class path resource [mycsvdir/] cannot be resolved to URL because it does not exist {code}  This can be solved by using a file:// prefix  Maybe just update the docs? "
Answer: 1376.0

User story: "The batch jobs use different defaults compared to some of the sink/source modules.  filehdfs puts data in a /data directory with files named after the stream using a .log file extension. The hdfs sink puts files in an /xd/<streamname> directory using .txt as the default file extension.  filehdfs needs a more descriptive naming"
Answer: 3240.0

User story: "see discussion at https://github.com/spring-projects/spring-xd/commit/2f0e80b5e337b71c9c70de510a44d2f050d10fa7"
Answer: 993858.0

User story: If we have default values from Container/Admin options, then they can not be overridden by the system properties or system environment.   Currently, the only default we have for the Container/Admin options is for "jmxEnabled" option and since it is a boolean it can never be overridden by sys/env property XD_JMX_ENABLED.  I think we need to make sure there are no default values assigned for the non-boolean Container/Admin options and handle the boolean type option separately.
Answer: 17589.0

User story: "Add docs to section   https://github.com/spring-projects/spring-xd/wiki/Batch-Jobs#pre-packaged-batch-jobs"
Answer: 239.0

User story: "The PropertyResolver needs to follow the below precedence order on PropertySources when resolving the module properties:  From lowest to the highest order,  0 application.yml 1 applicaiton.yml fragment 2 property placeholders 2a  property placeholder under 'shared' config directory  2b property placeholder under module/(source/sink/processor)/config directory 3. environment variables 4. system properties 5. command line   "
Answer: 109454.0

User story: "--transport as an alias for --controlTransport"
Answer: 23036.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Update to spring-data-hadoop 2.0.0.M5 when it is released and remove the temporary DatasetTemplateAllowingNulls in spring-xd-hadoop  We should also review the supported hadoop distros - think we should support anything that is current/stable: - hadoop12 - hadoop22 - phd1 (PHD 1.1) - hdp13 - hdp20 - cdh4 "
Answer: 81754.0

User story: "When using @Value for providing a default value in a module options POJO, make it so that the REST API (and hence the module info command) advertises that   1) the expression was ${foo.something} 2) to the best extent possible (value may come from another property source), tell which config file it came from (introspecting the @PropertySource annotation)"
Answer: 243556.0

User story: "However this is triggered (depending on whether https://github.com/spring-projects/spring-xd/pull/477/files is merged yet or not), jmx seems to be broken because of duplicate beans / mbeans names"
Answer: 31613.0

User story: "Labels should only be used help uniquely identify a module in a stream.  The stream definition a | x: b | x: c | d should throw an error since the label x is applied to two modules.  Also ambiguity exists with a stream definition such as   http | transform | transform | filter | hdfs  since a module with the name 'transform' will exist twice, meaning a tap on transform will result in message from both transform modules.  To make the naming unique and the usage with taps, the following naming strategy is proposed demonstrated by example.  http | transform | transform | filter | hdfs http, transform.0, transform.1, filter, hdfs  If a use tries to tap on transform, an error would be shown saying that  you could try to tap on transform.0 or transform.1 or alternatively use labels.  http | transform | filter | transform | hdfs http, transform.0, filter, transform.1, hdfs  http | x: transform | filter | transform | hdfs http, x, filter, transform, hdfs  "
Answer: 62530.0

User story: "Update dependencies to spring-data-hadoop 2.0.0.M4"
Answer: 88.0

User story: The current behavior when there are "global" external defaults to module options is to set them in the placeholder construct: ${foo:${the_default}} where ${the_default} is sourced from some properties file.  The downside is that the module options infrastructure is unaware of them.  Provide support for such defaults (at least when using PojoModuleOptions) in the form of  * Annotate a field (or the setter?) with @Value("${the_default}") * (maybe) Annotate the pojo with @PropertySource to indicate the location of the properties file * (maybe) come up with a general naming scheme for the properties file
Answer: 37270.0

User story: "Expected benefits are --key<space>value as well as --key=value on the command line (eg XD-1108)  nice usage screen  "
Answer: 23039.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: XD container's id is set to use its application context id which is derived from:  ${vcap.application.name:${spring.application.name:${spring.config.name:application}}}:${vcap.application.instance_index:${spring.application.index:${server.port:${PORT:null}}}}  With the *default* values[the PORT is not set and embedded tomcat uses local port], the launcher id is set to "application:0"  When I have multiple launchers then all the launchers have the same id as "application:0" which doesn't seem correct.  Do we need to use the Id that is generated at the XDContainer's constructor here?  public XDContainer() {   this.id = UUID.randomUUID().toString();  }  
Answer: 1887.0

User story: "The Gemfire CQ source needs some enhancements:  * enable locator configuration * consider decoupling from JSON. Currently designed to work with gemfire-json-server to avoid dependence on specific domain objects on the client and server side. So produces json strings from PdxInstance(s) stored in the cache.  "
Answer: 821157.0

User story: "We should standardize on the options between modules:  idleTimeout - timeout rolloverSize - rollover  Also, need to standardize on unit used for timeout - should this be s or ms? "
Answer: 825288.0

User story: "Create a script to sanity check JMS and MQTT"
Answer: 26547.0

User story: "Currently, the JobPlugin extends AbstractPlugin and the AbstractPlugin has got lots of unused code (like it doesn't do anything with preProcessSharedContext()) in there. "
Answer: 99279.0

User story: "Support all available options"
Answer: 1453.0

User story: Instead of using jobExecutionId and stepExecutionId as two separate options for the "job execution step progress" command, we can have a single option with id mentioned as (jobExecutionId:stepExecutionId)
Answer: 831181.0

User story: "Currently local is not a supported data transport for the container. It should be an option. Note that local is not valid for control transport for a standalone container. So we need to revisit the current semantics that default the control transport to be the same as the data transport, i.e. ,--transport=local should fail. "
Answer: 17391.0

User story: "Need to clarify if this means alternate transports within a stream, e.g   source |[rabbit] | processor |[redis]| sink   or specifying that a stream use an alternate transport to the one configured for the container.  "
Answer: 66100.0

User story: "The TriggerSourceOptionsMetadata class should be able to use an actual Date object, thanks to Spring binding conversion.  BUT, the ${date} construct will receive a toString version of it. Make sure this works properly"
Answer: 57906.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "The initial parsing of a stream/job definitions into a list of ModuleDeploymentRequests needs to be transformed into a Physical Deployment Model that takes into account   1) module co-location 2) partitioning 3) number of instances 4) node assignment  an potentially other data related to the runtime properties of a module (e.g. concurrency settings)   The an external DeploymentManifest will be used to capture this information.  A deployment of a stream or job will then need to optionally provide a reference to deployment manifest."
Answer: 10843.0

User story: Base matching algorithm on the model used in http://research.cs.wisc.edu/htcondor/   Jobs/Stream - specify their requirements and preferences Nodes - specify their requirements and preferences  e.g.    A job/stream module "requires" a linux x85-64 platform and "prefers" the machine with the most free memory  A node "requires" that only only can run jobs when there is 25% or more free memory and it "prefers" to run stream modules over job modules.  The requirements and preferences are represented as SpEL expressions in a "Advertisement" data structure.  There is a 'require' expression and a 'preference' expression.   Matching occurs between Node Ads and Job/Stream Ads so that the requirements of both Ads evaluate to true and the matching nodes are ranked according to the preference expression.  The Job/Streams Ads can make use of well defined attributes about the nodes, such as it's memory/cpu usage.
Answer: 204083.0

User story: "Each node in the cluster advertises itself and the admin node listens to these ads and creates groups out of them.  The deployment of jobs and stream processing can then be deployed onto a specific group and specific nodes within the group.  The project https://github.com/spring-projects/spring-data-grid is the start of this model."
Answer: 192812.0

User story: "For several Batch Job related JSON endpoints, we serialize too much information."
Answer: 838389.0

User story: "When a ModuleOption is backed by an enum, change the (currently String) type representation to be the possible values  ie java.lang.String -> String but traffic.Light -> Red | Green | Orange"
Answer: 1037262.0

User story: "This causes intermittent test failures when testing streams with other transports since ModuleDeployer receives duplicate requests from multiple threads. Fix is to check for local transport before invoking setUpControlChannels()"
Answer: 320.0

User story: "* need to add a -Dxd.home=$XD_HOME to the start scripts else all files will write to the /logs directory. * Need to update .bat files to use % for env variables instead of $. * Need to rename logger.config to logging.config so that boot will pick up the log config files. * Admin needs to use xd-admin-logger configs instead of xd-container-logger * Renamed logging file for singlenode from admin.log to singlenode.log"
Answer: 3519.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "See https://github.com/spring-projects/spring-xd/pull/415#issuecomment-29024329  This test should be created so that it reproduces the failure and then turned off, so that when we switch to the new HDFS writing code  "
Answer: 2567.0

User story: "EC2 Deployer  Needs to change its configuration behavior to use environment variables vs. the property files * Remove ConfigureSystem class, since we will use environment variables instead * Allow users to set environment variables via the xd-ec2 properties. * If properties are not present use those that are available in the application.yml * Utilize JClouds environment variable setup features to implement this behavior."
Answer: 22908.0

User story: "This could be inside gradlew or a .settings file."
Answer: 2748.0

User story: "This is a very big story, needs some planning/discussion before starting work.  Should be able to be implemented as a plugin. "
Answer: 90891.0

User story: Following merge of XD-953, provide module options using the "simple" approach where applicable
Answer: 94611.0

User story: Example: {noformat} xd:>module delete --name sink:file 12:31:19,495  WARN Spring Shell client.RestTemplate:566 - DELETE request for "http://localhost:9393/modules/sink/file" resulted in 500 (Internal Server Error); invoking error handler Command failed org.springframework.xd.rest.client.impl.SpringXDException: Cannot delete non-composed module sink:file {noformat}  The WARN log is redundant with the command result and should be silenced
Answer: 11.0

User story: "Following merge of XD-1109.  See discussion at https://github.com/spring-projects/spring-xd/commit/eaf886eab3b2ef07da55575029ccabb2c8a36af9#commitcomment-4701947"
Answer: 130118.0

User story: "2 forces at heand here: * Spring binding/validation itself * jsr303 (for eg @NotNull)"
Answer: 305588.0

User story: "We should we centrally standardize on date/time formats so that we don't create inconsistencies, and follow ISO 8601 internally. Internally we should only work with UTC (or make that the default config option).  Ultimately, whatever the user sees is just a formatting concern."
Answer: 335891.0

User story: "We need to create a shell script that calls the batch DB creation sql files for the JDBC option selected.  "
Answer: 15615.0

User story: "We no longer validate the --hadoopDistro options in the xd scripts. Seem sthe classes doing this validation were removed for boot.  We do this validation in the xd-shell script"
Answer: 70574.0

User story: "We have observed in unit tests (see AbstractSingleNodeStreamIntegrationTests) that(Redis/SingleNode) occasionally fail. The root cause must be investigated further but there is some evidence to suggest that the control messages (ModuleDeploymentRequests) are not always received and handled by the ModuleDeployer. This does not produce an error but results in runtime stream failures. This problem may be resolved as part of the planned Deployment SPI but is being tracked here until we are certain that it has been resolved."
Answer: 83563.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "ApplicationContext ID generation is difficult in general.  Cloud Foundry solves this problem for us by providing unique instance ids to all running instances of an app. I don't suppose that helps much in the general case though, and we need something (a rule of thumb) that is unique and preferably deterministic, so that nodes retain their ID across process and connector restarts.  In Cloud Foundry the instance id plays a vital role (and will be automatically picked up by the app and applied - need to look at how that plays in a context hierarchy). User can set the context id manually using {{spring.application.name}} and {{spring.application.index}}."
Answer: 851494.0

User story: "Spring Boot support port scanning if you set server.port=0 (and disable with -1), so we could make that the default for the container node."
Answer: 455.0

User story: The following keys remain after running the test suite:  {code} redis 127.0.0.1:6379> keys * 1) "containers" 2) "containers.application:9292" {code}  
Answer: 27348.0

User story: "Currently, the JobRepoTests use the same batch job repository that the XD runtime uses. Since the batch job repo doesn't delete the job instances, there would be stale data from this test. "
Answer: 5124.0

User story: "Wherever they come from (cmd line args or ENV_VARS), options such as transport, analytics, etc should be validated and issues should be reported to users"
Answer: 5412.0

User story: "Restore --foo=bar as well as --foo bar  Validation of values should be done as a separate story"
Answer: 151145.0

User story: "Currently, the tests use instantiated DistributedJobService object instead of a simple mock. We can just use mock object for the tests."
Answer: 446.0

User story: "Even though it may be hard to come up with a mqtt broker, an easy test that should be automated is  somesource | mqtt --topic=foo  with   mqtt --topics=foo | somesink   And asserting that what is emitted to somesource ends up in somesink.  "
Answer: 148790.0

User story: "Would be nice to have some kind of regression testing on the jdbc sink, as it becomes more prominent in XD.  Use of an in memory db where we expose eg a JdbcTemplate to assert state"
Answer: 148720.0

User story: "would be good to have a general feel for the general performance of these two options.  Redis can run on the same node as the benchmark."
Answer: 3479.0

User story: "The way we now include various Hadoop distributions is cumbersome to maintain. Need a better way of managing and isolating these dependencies on a module level rather than container level."
Answer: 1059162.0

User story: "Currently, the BatchJobsController and BatchJobExecutionsController are not HATEOAS compliant and we need make them so."
Answer: 9454.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This should go in the first section of the Batch Job documentation.  Here is a rough suggestion  The lifecycle of a job in XD.  1. Register a job module with the MoudleRegistry by putting a XML/jar files in the $XD_HOME/modules/jobs directory. 2. Create a job definition from a job module by providing a name and properties that apply to all job instances can be configured at this point.  The job is not yet deployed 3. Deploy the job to an xd-container.  A job instance can not be created by sending a message to a job queue that contains optional runtime job parameters 4. Launch a job by sending a message to the job queue with job parametres.  A Job Instance is created, representing a specific run of the job.  A Job Instance is the Job Definition plus the runtime job parameters.  You can query for the Job Instances associated with a given job name 5. The job is executed creating a Job Exection object that captures the success or failure of the job.  You can query for the Job Executions associated with a given job name. 6. Undeploy a job.  This removes the job from xd-container."
Answer: 362089.0

User story: "The automatic deployment of the job makes it harder to understand the lifecycle of the job and also does not allow for the opportunity to define any additional deployment metadata for how that job runs, e.g is it partitioned etc."
Answer: 3656.0

User story: "BatchJobsController.listForJob should be 'executionsForJob' BatchJobsController.jobInstances should be 'instancesForJob'  The JavaDoc for the class and each method should be more descriptive about their functionality   "
Answer: 713.0

User story: "Develop out a Proof of concept for review that allows users to easily create a new module to Spring XD. Key features to be enabled:  1. Allow existing modules to be included as a classpath dependency 2. Consolidate shared libraries in existing modules (e.g. a shared lib for all gemfire modules) 3. User develops a module as a normal Java project 4. User's project can then be added to a runtime container in the same way (as a dependency)  Nice to have:   1. at development time container can run continuously and pick up changes from user's module project. 2. Java config for a module. 3. command line functionality to create project scaffolding.  "
Answer: 504071.0

User story: "This is along the lines of what is in this blog post  http://coreyreil.wordpress.com/2012/12/21/spring-batch-creating-an-ftp-tasklet-to-get-remote-files/  Note that there have been some new developments in SI to get at the underlying stream for FTP.  The way to test this is to create a new batch job in XD that has this as it's tasklet.  Going forward the target file system will also be HDFS."
Answer: 106457.0

User story: "Migrating to boot dropped the XD banner and its info.  Can be restored using eg a boot Initializer and removing the default boot banner"
Answer: 103112.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Summary says it all. When starting, we now get {noformat} SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/Users/ebottard/.gradle/caches/artifacts-24/filestore/org.slf4j/slf4j-log4j12/1.7.5/jar/6edffc576ce104ec769d954618764f39f0f0f10d/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/Users/ebottard/.gradle/caches/artifacts-24/filestore/org.slf4j/slf4j-log4j12/1.6.1/jar/bd245d6746cdd4e6203e976e21d597a46f115802/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory] {noformat}  Most certainly introduced by 1c4817ee60ae9325f6394dcc78aa803c47818546 or 72baec92f2e7bbe860b4a9dc6c994536c1670881 "
Answer: 103119.0

User story: "Change the default port since it conflicts with the default port for the http source"
Answer: 14249.0

User story: for example, the following should work:  {code} xd:>stream create a1 --definition "queue:a > transform --expression=payload+'-a' | log" Created new stream 'a1'  xd:>stream create b1 --definition "queue:b > transform --expression=payload+'-b' | log" Created new stream 'b1'  xd:>stream create s1 --definition "http | router --expression=payload.contains('a')?'queue:a':'queue:b'" Created new stream 's1'  xd:>http post --data "ha" > POST (text/plain;Charset=UTF-8) http://localhost:9000 ha > 200 OK  // log shows: "ha-a"  xd:>http post --data "hi" > POST (text/plain;Charset=UTF-8) http://localhost:9000 hi > 200 OK  // log shows: "ha-b" {code}  This needs to be tested against all transports (local, redis, and rabbit) 
Answer: 10841.0

User story: "Use of dot in property name prevents the user from specifying a value in stream definition  Also, defaults are repeated at .xml and .properties level"
Answer: 6024.0

User story: "Looks like we need to spend a cycle on Asciidoc - as we still have the author-tag-issue - I thought we can simply upgrade the asciidoctor-gradle-plugin to 0.7.0 (currently 0.4.1) but that breaks the docs being generated."
Answer: 13925.0

User story: "(apologies if a ticket already exists for this, but I didn't see one)  I spun up the Hortonworks Data Platform 2.0 sandbox, but see it isn't supported by Spring XD yet.  How hard would it be to add these Distro's in?  Is it just a matter of dropping in a lib folder for hadoop22 and/or hdp20, and allowing those and options to be passed in via the --hadoopDistro option?  I'm currently trying to work through the following tutorial, but using the HDP 2.0 sandbox instead of the 1.3 sandbox  http://hortonworks.com/hadoop-tutorial/using-spring-xd-to-stream-tweets-to-hadoop-for-sentiment-analysis/  Thanks!"
Answer: 135228.0

User story: "Currently, the bootstrap.less file has all the styles that the bootstrap supports. But we should only add/compile the LESS that are needed by XD UI."
Answer: 10266.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "The table background color on the Job Definition Tab is green while the others tabs have a white background.  They should be consistent."
Answer: 112409.0

User story: "Job gets a empty key:value pair when launching the job from the admin-ui."
Answer: 112220.0

User story: "I know that the feature is not ready, but we either should post a message to the user that the feature is not available or hide the button"
Answer: 112413.0

User story: "The deployment tab does not reflect the current state of the jobs.  User must hit browser refresh button to make it work."
Answer: 112416.0

User story: e.g. see comment on PR #390: https://github.com/spring-projects/spring-xd/pull/390/files#r7563787  In that case, it's "delete" in one place and "destroy" in another. There are other cases as well.
Answer: 211693.0

User story: note from PR #365:  {quote} We should probably create a new story to (at least) rename "module display" to "module showconfig" or something, but possibly even reconsider it altogether. In some sense, it's even violating the encapsulation of ModuleRegistry. It wont work for java-config style modules or spring-integration Groovy DSL modules. Personally, if anything, I'd rather see those config files themselves exposed as part of an admin UI. What you are doing with the options here fits better with the encapsulation principle and the fact that typical usage should not require detailed knowledge of the actual underlying configuration of a Module. {quote}  
Answer: 314077.0

User story: note from PR #365 - which has been merged - providing the initial level of support...  Pending issues (to be addressed in another PR?): - [x] complex case - [x] default values for complex case, when option is not surfaced back to the module (eg "suffix" in our canonical example) - [ ] plugin provided options and values - [ ] descriptive defaults instead of actual defaults (e.g. \<use stream name\>) - [ ] JSR303 Validation  
Answer: 116353.0

User story: "this would elminate dependencies that are currently in the codebase, such as:  * RESTModuleType and ModuleType enums * ModuleOption and DetailedModuleDefinitionResource.Option  "
Answer: 1072995.0

User story: "see comments on this PR (which is part of the code that needs to be refactored): https://github.com/spring-projects/spring-xd/pull/390 "
Answer: 36240.0

User story: "Currently the parser returns a List<ModuleDeploymentRequest>, and the deployer works with that list directly. We need a higher level parser result (e.g. DeployableStream - or probably a better name after some thought) that can encapsulate that list while also enabling metadata to be added. That metadata may be helpful for composite module information as well as the module dependencies of a given stream (including any composed modules within that stream)."
Answer: 874213.0

User story: "The ModuleOptions PR currently uses FQN for types (eg java.lang.String)  Would be nice to have support for short names for common types, both in the properties files and the annotation"
Answer: 42912.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Make sure the sinks and jobs work against Pivotal HD 1.1"
Answer: 6113.0

User story: "See the discussion in https://github.com/spring-projects/spring-xd/pull/370  There are now various superseded classes and tests which we no longer need."
Answer: 17085.0

User story: "Although composition of a module out of an already composed module seems to work at the 'module compose' level, trying to deploy a stream with that more complex module fails with   at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)  at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  at java.lang.Thread.run(Thread.java:724) Caused by: java.lang.IllegalArgumentException: each module before the last must provide 'output'  at org.springframework.util.Assert.notNull(Assert.java:112)  at org.springframework.xd.module.CompositeModule.initialize(CompositeModule.java:132)  at org.springframework.xd.dirt.module.ModuleDeployer.deploy(ModuleDeployer.java:234)  at org.springframework.xd.dirt.module.ModuleDeployer.deployModule(ModuleDeployer.java:224)  at org.springframework.xd.dirt.module.ModuleDeployer.handleCompositeModuleDeployment(ModuleDeployer.java:180)  at org.springframework.xd.dirt.module.ModuleDeployer.handleMessageInternal(ModuleDeployer.java:129)  at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:73)  ... 63 more"
Answer: 158789.0

User story: With the following semantics (assuming http | filter | transform composition):   * Fully qualified names always available (eg filter.expression)    * using module type as key    * or label if ambiguity * Simple names available if no ambiguity (eg here "port" refers to http.port)  As per discussion:  VIII) Use of “--expression” option in composed module “filter | filter” Should not be supported (require FQN always) Should pertain to first filter module (always) Should pertain to all modules with an “expression” option (here: both filters) Should fail if not qualified and ambiguity. Use label.expression (or type.expression, eg if we had “filter | transform) (see VII ⇒ nesting1.nesting2.nesting3.expression) (MF)  VIII) Use of “--expression” option in composed module “http | filter --expression=something | transform” Should not be supported (already valued) Should pertain to first filter module (always) Should pertain to all modules with an “expression” option (here: both filters) Should fail if not qualified and ambiguity. Use label.expression (or type.expression, eg if we had “filter | transform) (see VII ⇒ nesting1.nesting2.nesting3.expression) (MF) 
Answer: 160269.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Provided it is not currently used in any stream:  V) Attempt to destroy a composed module Should not be supported at all Should not be supported if involved in at least one stream (EB?, MF!) Should be supported and have no other consequences whatsoever (see IV) (EB?) Should be supported and invalidate/destroy streams involving it "
Answer: 7684.0

User story: "As per discussion, any attempt to create something that would collide with existing should fail:  II) Attempt to create a composed module with same name as an already existing, not composed module, with same type should fail (EB, MF) should work and shadow previous module from now on  III) Attempt to create a composed module with same name as an already existing composed module, with same type should fail (EB, MF) should work and shadow previous module from now on should work and retroactively change definitions of streams with that module "
Answer: 647.0

User story: This relates to XD-871 which provides a good scenario.   >stream create s1 --definition "http | log --deploy"  >stream create s2 --definition "http | log --deploy"  The second command results in an error message that the port is in use but the stream definition is still saved. Since create + deploy is a logical unit of work, it should follow transactional semantics. In other words if the deploy fails, the repository should be rolled back (or a compensating destroy should be performed).  Note this should not be handled the same way if create and deploy happen separately. In that case, the stream definition should remain.
Answer: 306920.0

User story: Add a module that can act as a tcp *client* (as opposed to our current tcp module, which acts as a server, waiting for an incoming connection)  Also, the module should allow to send "commands" to the remote server. The typical minimal case for such a protocol is to send "PING" messages, but a stateful mechanism should be put in place for more complex cases.
Answer: 1210.0

User story: * rename spring-xd-extension-hdfs to something else, as it seems it is all spring "data" stuff and is not coupled to xd. But leave it in extensions/ for now * rename and move spring-xd-hadoop inside extensions (maybe to spring-xd-extension-hadoop (or hdfs)) * make hadoop related modules depend on the latter (which itself will depend on the former)
Answer: 43779.0

User story: "Use a modal dialog to specify runtime parameters. There should be a little text are that gives hints as to the spring batch parameter key/value conventions, e.g. for type.  Might be a good idea to have a checkbox that lets you select to 'auto increment' job instance number.  4 columns key, value, type, identifying and an 'add parameter' button that adds a new row.  This would appear as a modal dialog box, polling of the state of the deployments would be suspended while the job parameter modal dialog box is shown.  "
Answer: 10646.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Specify the default URL as:  {code} urlRoot: location.protocol+'//'+location.hostname+(location.port ? ':'+location.port: '') {code}"
Answer: 4292.0

User story: "The current admin UI uses bootstrap 3.0.0 which provides responsive design. We need to expand our scope to support all supported user agents.  This requires changes to use user agent specific layout for the UI views."
Answer: 26052.0

User story: "From XD-1023, the job status(deployed/undeployed) is available from JobInstance Repository and a job can be deployed/undeployed correctly.   Implement Job deploy/undeploy for a given job from JobDefinitions page and indicate status of the job definition (deployed/undeployed)."
Answer: 1268.0

User story: "The current (XD) uses an inadequate {{MessageRedisSerializer}} when {{extractPayload}} is false (not currently being used). When porting this to SI, the serializer will be dropped.  Suggest creation of Kryo serializer for Messages for when Redis source/sinks are created."
Answer: 13095.0

User story: "Job deployment currently goes through an overloaded version of deploy() that takes 4 parameters. This prohibits job handling code from benefiting from common behavior (and eg currently breaks deployAll)  Given that the 3 additional parameters are in fine handled as module parameters, let's push them to the job definition, known at creation time, rather than at deployment time (as it does not really make sense to change those between deploys)"
Answer: 3053.0

User story: The module list command currently has a very simplistic two column display of (module name, module type). The is not very readable.  Switch to a 4 column display: (Sources, Processors, Sinks, Jobs)  Additionally, mark composed module [e.g. "myhttp (c)"]
Answer: 132438.0

User story: "Create a composed module Create a stream that uses that module Try to undeploy the stream. Kaboom  The dispatch is not correctly implemented in ModuleDeployer"
Answer: 171714.0

User story: "ModuleDeployer has many methods with very similar names that are hard to understand.  Moreover, there is a substantial amount of duplicated code that should be extracted in sub methods with descriptive names.  One should even consider splitting the class  "
Answer: 59435.0

User story: "Probably the cleanest approach is to provide a properties file in the xd config directory that enables this globally, e.g., json.pretty.print=true.  This will require some refactoring of the ModuleTypeConversion plugin, i.e., use DI in streams.xml"
Answer: 543819.0

User story: "Create a reusable responsive UI layout to render the PagedResources returned from REST endpoint.   As part of this, try upgrading the bootstrap to 3.0.0 and use the responsive styles offered in it."
Answer: 9021.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Currently HSQLDB is the only option for batch jobs.  This should be configurable so that a user may select another JDBC data store option.    Steps: * hsqldb.properties needs to be changed to batch-jdbc.properties * hsql prefixes should be changed to batch-jdbc * JDBC Connection String needs to be configurable * JDBC Driver needs to be configurable * The Setup Scripts to be used for spring batch need to be configurable. * HSQLServerBean should be renamed to something batch-jdbc.properties  Tests: Should be able write tests that support HSQLDB"
Answer: 57606.0

User story: "Currently, the jobs definition list REST endpoint doesn't include deployed/undeployed status on a given job."
Answer: 10836.0

User story: "On clicking the job detail page, we should display all the step executions associated with the specific job execution in a table view."
Answer: 282915.0

User story: On clicking "details" link on a job execution row, user should see the job details.  Job detail page will show all the information about the job, where as the table listing of jobs on the Execution tab may have omitted some columns or aggregated values to convey information more easily.
Answer: 273300.0

User story: "On clicking the “Executions” tab, user should see the list of all batch job executions. There should be options to filter job executions by few criteria such as by “Job name”, “execution time” etc., "
Answer: 159258.0

User story: From the Deployed jobs page, by clicking the "Schedule" button on a specific deployed job row, user should be able to schedule this job with: 1) Cron trigger (with cron expression) as a source to job launching named channel 2) Fixed rate/delay trigger as a source to job launching named channel  
Answer: 288722.0

User story: From the Deployed jobs page, user should be able to click on the "Launch" button on a specific job and specify the Job parameters as key value pairs in the text box and we will convert that into JSON string as JobParameters into JobLaunch request.  
Answer: 16585.0

User story: "On clicking a specific job name in the deployed jobs list, we need to redirect the user to show the list of all the job executions on that job.  User should be able to navigate back to the deployed jobs list."
Answer: 898150.0

User story: "On clicking the “Deployed Jobs”, we can have a table view of all the deployed jobs. This is again a responsive table layout with all the job definitions with status “deployed”. The deployed XD job corresponds to a single batch Job Instance.   This story addresses the UI layout changes to display existing JobInstance information."
Answer: 16256.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Create a tab view with tabs “Job Definitions”, “Runtime Jobs” (Deployed Jobs?, “Job Instances” (Is Runtime Jobs a better name here?) and “Job Executions”. On clicking “Job Definitions” tab, we can have a table view of job definitions. Since we bootstrap.js, we can have a responsive table layout to list all the available job definitions. At the REST layer, “/jobs” provides the list of job definitions. We can expand the JobsController list()’s QueryOptions to add more criteria (especially to list JobDefinition’s status (Deployed/Undeployed). Also, this is the UI implementation for the shell command “job list” "
Answer: 11207.0

User story: "Related to https://jira.springsource.org/browse/BATCH-2109  DistributedJobService#listJobExecutionsForJob overrides  SimpleJobService#listJobExecutionsForJob  and does not include the *StepExecution*s. This is due to serializion issues with Jackson.   In order to fix this, we need to add a Jackson MixIn. "
Answer: 2578.0

User story: "Need some sample usage, docs for   https://github.com/spring-projects/spring-xd/tree/master/modules/source/gemfire   "
Answer: 21610.0

User story: "Support for partitioning on a field, e.g. date."
Answer: 299591.0

User story: Some tests (esp. ModuleClasspathTests.testModuleWithClasspathAfterServerStarted) seem to fail because of a race condition.  Add a Hamcrest matcher that knows how to read the content of a FileSink|Source and refactor those to read like e.g.  assertThat(fileSink, eventually(hasContent("foo)))  
Answer: 11829.0

User story: "Writing POJOs using Kite SDK "
Answer: 899933.0

User story: "Support for using compression when writing Sequence Files  Either block or record-based compression. "
Answer: 899958.0

User story: "Support for writing Sequence Files  Without Compression  Need a means to specify the key/value to be used "
Answer: 899959.0

User story: "Same setup as XD-987 for ItemReader and ItemProcessor, but should write to HDFS.    One can assume that the table structure has been created already external to the batch job execution."
Answer: 18875.0

User story: "The ItemReader will read multiple files from HDFS and the data will be converted to a tuple data structure The ItemProcessor will be a no-op groovy script. The ItemWriter will write the data to a MongoDB collection ** A TupleToDBObject converter will need to be developed.  *the sample job should be documented*"
Answer: 18871.0

User story: Same processing as XD-984, but the job instacne is launched via an event from the input file source.  Supporting a single file per job launch is OK.  > job create blah --definition "filehdfs"  > stream create csvStream --definition "file --ref=true --dir=/Users/<USER>--pattern=*.csv > job:blah"     *the job should be documented*
Answer: 18707.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Create a sample batch job for inclusion in the distribution that will perform the following tasks.  ItemReader * Read a from a directory with multiple files (configurable) * Support for CSV (assume first line has header values) * Convert to tuple data structure ItemProcessor * Provide groovy based no-op ItemProcessor.  (configurable) ItemWriter * Write to JDBC. ** Provide  ** Assume there is an DB instance running somewhere, specify connection info (configurable)  **The sample job should be documented** "
Answer: 18714.0

User story: "We used to have a shared guava-11.0.2.jar dependency in the lib dir. That's no longer there so hadoop distros that require this now fail (at least any hadoop 2.0.x based ones)  We should also upgrade to current Hadoop versions (Hadoop 2.2 stable)"
Answer: 50079.0

User story: "*Update the Deployer class to add the following methods* * RunningInstance  deployContainer  * For each of the containers: ** Using XD-977 install distribution ** Setup XD_HOME variable ** Create configurator directory ** Copy the configurator to containers ** Run Configurators ** Verify that configuration files are setup correctly ** start container server ** Report if container started. (using jmx/Jolokia, if available) If it didn't start report failure but continue. ** Report public DNS name of container   * Integration Testing ** Verify that config files have been setup properly ** For each container: *** Verify container has been started *** Verify that container is working by creating a stream in admin (trigger|log).  Verify that the log on the container is being updated.  "
Answer: 41237.0

User story: "* Create a Deployer class has methods ** RunningInstance  deploySingleNode *** takes into account machine size as specified in properties file ** void  destroyAllInstances()   *** or whatever JClouds returns from the destroy call ** ctor gets passed in the root boostrapping credentials. * Install Script Steps ** Setup XD_HOME variable ** Make sure privileges are set to ubuntu not root. ** start up redis and rabbit using ports as specified in xd-ec2.properties ** Use port watch to make sure they started ** Start singlenode after configuration. ** Display hostname of singlenode server ** Report successful and failed startup ** Hit root of xd-admin to see if there is a response on 9393 * Integration Testing ** Verify that config files have been setup ** Verify XD has been started ** Verify XD can process a basic http post  "
Answer: 22694.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "* User specifies download distribution zip file from properties file.  See XD-969 for key-value pairs * Copy the distribution from the shared EBS/S3  the ebs volume assigned to the each node/admin instance  .   ** If not on shared ebs/s3 pull from http site specified by user and put on the shared EBS volume.  ** Unzip the distribution from on the ebs volume for the instance to the /home/ubuntu directory ** make sure privileges are set to ubuntu not root.   How to verify it works * Create a JUNit style integration test that ** Deletes a known .zip distribution from EBS/S3. ** Invoke the application functionality (should be a 1 liner) that will start up the instance and download the .zip distribution from the URI provided in xd-ec2.properties.  Verify the file is now in EBS/S3 and also on the instance ** Tear down created instance ** Create new instance passing in the same URI of the .zip distribution.  Verify as before "
Answer: 22728.0

User story: "* Create a Spring application context.  (XML or Java, dealers choice…) * Use XD eclipse code format policy * Create Source Package structure * Create Test Package Structure * Gradle build * JClouds and Spring deps  "
Answer: 12786.0

User story: "Get a java.io.File and copy it into HDFS.  Could be text or binary.  Write compressed with Hadoop and third party codecs   see: (XD-277, XD-279)  should initially support:  - bzip2    - LZO  "
Answer: 901486.0

User story: "Automated test will use directly use the Deployer class * asserts on basic info of RunningInstance ** check that EBS was mounted ** that application was unzipped ** redis and rabbit are running via port checks  * http requests on admin port for  ** root path ** list of modules * @AfterClass that will look for the cluster name and terminate all instances Look at ‘live’ tag in JClouds tests for some additional tactics "
Answer: 50146.0

User story: "*Update the Deployer class to add the following methods * ** RunningInstance  deployAdminServer  * The install script steps: ** Using XD-977 install distribution ** Setup XD_HOME variable ** start up redis and rabbit using ports as specified in xd-ec2.properties on admin server ** Create configurator directory ** Copy the configurator to containers ** Use port watch to make sure they started ** start admin server ** use port watch to make sure the admin started on 9393 ** Report if admin server started.  If it didn't start abort install. ** Report public DNS name of admin-server    * Integration Testing ** Verify XD admin has been started *** Create a basic stream (trigger>log)and make sure we get a success code from xd admin was received. *** Query the redis to see if the stream was created.  "
Answer: 30726.0