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: "Currently, you have to set the default name node every time your start the shell. We should do 2 things:   - Provide a default Name node Set Default Hadoop Name Node for Shell: hdfs://localhost:8020 - Should we provide some form of persistence? It kind of sucks that you have to re-specify the name node every time the shell starts up  {code} xd:>hadoop fs ls / You must set fs URL before run fs commands {code} "
Answer: 841550.0

User story: "Model the API more akin to SpringXDOperations api."
Answer: 16.0

User story: Was following the (now updated) directions for gemfire-cq source.  xd:> stream create --name stocks --definition "http --port=9090 | gemfire-json-server --regionName=Stocks --keyExpression=payload.getField('symbol')" xd:> stream create --name cqtest --definition "gemfire-cq --query='Select * from /Stocks where symbol=''VMW''' | file" xd:> http post --target http://localhost:9090 --data "{"symbol":"VMW", "price":73}"  The double quotes were causing a problem with xd-singlenode  Aug 06, 2013 5:38:15 PM org.jboss.netty.channel.SimpleChannelUpstreamHandler WARNING: EXCEPTION, please implement org.springframework.integration.x.http.NettyHttpInboundChannelAdapter$Handler.exceptionCaught() for proper handling. org.springframework.integration.transformer.MessageTransformationException: org.springframework.integration.MessageHandlingException: org.springframework.integration.transformer.MessageTransformationException: Expected a ':' after a key at 22 [character 23 line 1]  at org.springframework.integration.transformer.MessageTransformingHandler.handleRequestMessage(MessageTransformingHandler.java:73)  at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleMessageInternal(AbstractReplyProducingMessageHandler.java:137)  at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:73)  Using single quotes inside the json brackets worked, need to investigate.
Answer: 8247.0

User story: Content-Type during transport transit is not the same as the content-type within modules.  "Real" transports always use byte[] which may contain raw byte[] from a source, a byte[] converted from a String (which may or may not already contain JSON), or a byte[] containing JSON converted by the transport on the outbound side.  The transport needs to convey which of these was applied on the outbound side so it can properly reconstruct the message.  Retain any content-type header that already exists in the message, and restore it.  For Rabbit, use normal SI/Rabbit headers to convey this information.  For Redis, add the information to the byte[].
Answer: 1675.0

User story: "When using Redis store, stored deployed streams should be deployed on container restart."
Answer: 364413.0

User story: "https://github.com/springsource/spring-xd/wiki/Sinks  should have 'rabbit' added to the list and also the corresponding section that shows some basic usage."
Answer: 1796.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: "http://static.springsource.org/spring-xd/docs/1.0.0.BUILD-SNAPSHOT/reference/html/#sources  should have 'file' added to the list and also the corresponding section that shows some basic usage."
Answer: 3418.0

User story: "http://static.springsource.org/spring-xd/docs/1.0.0.BUILD-SNAPSHOT/reference/html/#sources  should have 'jms' added to the list and also the corresponding section that shows some basic usage."
Answer: 2895.0

User story: "http://static.springsource.org/spring-xd/docs/1.0.0.BUILD-SNAPSHOT/reference/html/#sources  should have 'rabbit' added to the list and also the corresponding section that shows some basic usage."
Answer: 2141.0

User story: This may be an issue following the search/replace from curl to Shell, but for example, this documentation line does not work:  http post --target http://localhost:9000 --data "{\"symbol\":\"VMW\",\"price\":72.04}"  The backslash prior to quote is left in the payload (and hence Jackson chokes on it)  We need clear rules about quoting at the shell level
Answer: 3772.0

User story: The RichGauge section does not mention the "alpha" parameter in redis output, nor does it explain its meaning.
Answer: 4283.0

User story: Need to investigate why this is happening, normally setting  {code:xml} <gfe:client-cache close="false"/> {code} prevents the (singleton) cache from closing when the application context is closed. 
Answer: 3070.0

User story: "When running an ad-hoc job without the use of a trigger (adhoc or named).  The user has to wait for job to complete before receiving a success.  We need to launch a job and get a success back to the user letting them know the job has been launched.  for example --immediate"
Answer: 24860.0

User story: "Add CONTRIBUTING.md file, use the Spring Integration file as the basis."
Answer: 4003.0

User story: We need to fix the github wiki to use the xd shell command prompt "xd:>".
Answer: 4129.0

User story: "We need to add list/delete commands for the metrics:  InMemoryAggregateCounter FieldValueCounter Gauge RichGauge  Currently, the AbstractMetricsController class has the delete method to delete the metric from the repository. We can probably use the same for all the metrics."
Answer: 4067.0

User story: Add "counter delete" shell command. This also requires implementation of DELETE rest end point at CountersController.
Answer: 4199.0

User story: "The current flow of gradle tasks is confusing.  Suggest the following changes to simplify the flow.  1. Move the current task logic in zipXD to distZip 2. Have distZip depend on dist 3. Update the 'how to build docs' on the wiki 4. Make sure that the distZip task only shows up once in the list of gradle target. "
Answer: 2820.0

User story: "Keep track of named streams that were create and use @After to destroy them."
Answer: 394.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: Both Luke's original code and my refactored PR[1] (which uses same code snippet) seem to behave strangely.  Stored values seem fine, but the getCounts() method seems phony.  To test: 1) stream create foo --definition "time|log" 2) tap create bar --definition "tap@foo | aggregatecounter" 3) curl -H "application/json" http://localhost:8080/metrics/aggregate-counters/bar  this gives default bucketing (hourly) but chances are that they are empty. 
Answer: 19868.0

User story: "Sending data to an incomplete stream which is created using a named sink channel only works when using Redis (or Rabbit?, not tested). Since the in-memory version doesn't use a queue, it will fail if you are using xd-singlenode.  We should use a queue channel with unlimited capacity to allow messages to be sent before the full stream is created."
Answer: 8532.0

User story: "results in both in-memory and redis based definitions of RichGaugeService - can't satisfy autowiring because there are two candidates.  Had to change --analytics=memory to get the application context to load."
Answer: 3112.0

User story: From https://github.com/SpringSource/spring-xd/pull/161:  "The command shell needs to also support different hadoop distribution options. Perhaps the shell just uses a relative path to the location of xd/lib/"
Answer: 467.0

User story: http://localhost:8080:>hadoop config fs --namenode webhdfs://localhost:50070 http://localhost:8080:>hadoop fs ls / Hadoop configuration changed, re-initializing shell... run HDFS shell failed. Message is: org/mortbay/util/ajax/JSON  This was on a hadoop 1.0.1 install  The hdfs http interface was available  $ curl -i "http://localhost:50070/webhdfs/v1/tmp?op=GETFILESTATUS" HTTP/1.1 200 OK Content-Type: application/json Transfer-Encoding: chunked Server: Jetty(6.1.26)  {"FileStatus":{"accessTime":0,"blockSize":0,"group":"supergroup","length":0,"modificationTime":1365015846724,"owner":"mpollack","pathSuffix":"","permission":"777","replication":0,"type":"DIRECTORY"}} 
Answer: 101714.0

User story: "The current http command is of the form  http://localhost:8080:>post httpsource --target http://localhost:9090 --data 10   It isn't intuitive to think 'post', rather the command can be   http post --target http://localhost:9090 --data 10  which will allow us to have support for other http verbs and cleanly separate the namespace from 'hadoop' etc.  The RestShell from which this came was only concerned with http actions, so the leading command classification probably seemed superfluous. "
Answer: 1652.0

User story: "e.g. http://localhost:8080:>post httpsource --target http://localhost:9090 --data 10  I believe this will also help to avoid ugly syntax to escaping quotes for json as in the gemfire example."
Answer: 2077.0

User story: "Expected usage (ATM) would be  // sink channel called foo http | transform --expression=payload.toUppercase() > :foo // source channel called foo :foo > count | file"
Answer: 2227.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: DSL should be able to parse what is below, need tests (CLI integration tests) to ensure it is being mapped to an executeable stream.  myIntricateFlow = transform --expression=payload.toUppercase() | transform --expression=payload.toLowercase() http | myIntricateFlow | file obfuscateName = transform --expression=payload.replaceAll("${name}",XXX) twitter --query=Bieber | obfuscateName --name=Justin | file 
Answer: 2715.0

User story: "Create a reproducible series of steps or shell integration test. "
Answer: 1261.0

User story: "Show how to select a specific hadoop distribution when starting embedded/standalone XDContainer."
Answer: 4036.0

User story: "make sure nothing is broken - spot check using.  1) ticktock 2) twitter 3) gemfire   "
Answer: 11643.0

User story: "reproduce 1) Create a bad stream definition name 'bad' Try to recreate with the same name, but correct stream definitions.  The system will report that the stream already exists.  "
Answer: 20120.0

User story: "There is some overlap between the gauge and counter repository types and also between the domain resources used by the REST controllers (CounterResource, GaugeResource). The aggregate counter may wish to return a simple count value for the counter too, which would also be a simple integral value."
Answer: 1021603.0

User story: "It seems the html rendering of documentation is using a variable width font for some of the code (esp. [source,sh] apparently) rendering.  Weird thing though is that when mouse hovering over some of them, they went back to fixed width. See screenshot.  http://static.springsource.org/spring-xd/docs/current-SNAPSHOT/reference/html/#_start_the_runtime_and_the_xd_shell "
Answer: 44818.0

User story: the top-level URL works via simple curl (without an Accept header) or the browser:  {code} > curl http://localhost:8080  {"links":[{"rel":"streams","href":"http://localhost:8080/streams"},{"rel":"triggers","href":"http://localhost:8080/triggers"},{"rel":"jobs","href":"http://localhost:8080/jobs"},{"rel":"taps","href":"http://localhost:8080/taps"},{"rel":"counters","href":"http://localhost:8080/metrics/counters"}]} {code}  However, trying any of those links then fails, e.g.:  {code} > curl http://localhost:8080/streams  <?xml version="1.0" encoding="UTF-8" standalone="yes"?><errors xmlns:ns2="http://www.w3.org/2005/Atom"><error logref="HttpMessageNotWritableException"><message>Could not marshal [PagedResource { content: [links: [&lt;http://localhost:8080/streams/mqttdemo&gt;;rel=&quot;self&quot;]], metadata: Metadata { number: 0, total pages: 1, total elements: 1, size: 20 }, links: [] }]: null; nested exception is javax.xml.bind.MarshalException  - with linked exception: [com.sun.istack.internal.SAXException2: unable to marshal type &quot;org.springframework.xd.rest.client.domain.StreamDefinitionResource&quot; as an element because it is not known to this context.]</message></error></errors> {code} 
Answer: 15766.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: "Split plugin module processing into pre and post processing where preprocessing is done before the context is refreshed and post processing is done after the refresh, but before the start.  In the Stream plugin, wire the module into the {{ChannelRegistry}} during post processing, instead of using the {{ChannelRegistrar}}."
Answer: 276.0

User story: "Seems like the current file source results from an initial POC. Very few things can be parameterized, including the polled directory that needs to be in /tmp/xxx  To be useful in production, we might want to revisit"
Answer: 19622.0

User story: "FieldValueCounterHandler was first written to support setting several fields at once, but the current constructor / field-value-counter.xml does not use it.  Either leverage that feature or simplify code"
Answer: 268580.0

User story: Most of the infrastructure and code cleanup has been done for In-Memory Analytics. The only remaining issue is that, by including memory-analytics.xml from common.xml, we're actually creating e.g. a new InMemoryCounterRepository that is different from the one present in the Admin process space.  This story involves fixing that. It may actually be done as part of XD-353, handling the "local" transport as a special case (context inheritance) rather than import based on xd.transport
Answer: 26267.0

User story: "Currently many methods take module, group, index - defining a module instance; group and index can be encapsulated in {{Module}} so one arg can be passed around."
Answer: 1066.0

User story: "Use an 'undeploy' topic to broadcast undeploy requests to all containers.  Applies to Redis and Rabbit transports, not local.  Also, rename {{ModuleDeploymentRequest}} to {{ModuleOperationRequest}} with an enum {{DEPLOY}}, {{UNDEPLOY}}."
Answer: 12171.0

User story: "Investigate using transactions and pipelining to improve performance of both the inbound and outbound RedisQueue channel adapters. Involves testing against a pre-release of SDR 1.1 M2."
Answer: 1913.0

User story: "This requires to boostrap the singlenode admin server in process, submit commands to the shell programmatically, and assert on the results of executing the command."
Answer: 2051.0

User story: "This story corresponds to 3) & 4) in discussion below.     Currently, sink xml files define the Repository (hardcoded to be redis) and the services (tied to Redis as well!)   I want to:   1) Move those definitions out of the sink files, to somewhere shared by both admin and container   2) Make them aware of some configuration parameter (similar to the --store command line option)    3) Get rid of so-called Service layer (doesn't do much right now, and logic would better live in the 'Handler' IMO)   4) Have REST controllers depend on XRepository in all cases"
Answer: 1397.0

User story: "creating job defs, deploying jobs, undeploying jobs, deleting job defs"
Answer: 20442.0

User story: "creating triggers, deleting triggers"
Answer: 489814.0

User story: "creating taps, deleting"
Answer: 20345.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, delete, deploy streams..."
Answer: 10970.0

User story: "Existing code: https://github.com/ghillert/springone2012"
Answer: 73545.0

User story: "Still keep existing one."
Answer: 50395.0

User story: "Currently, living at the root of the project, those files don't benefit from IDE SI awareness. Make it so that they belong to a java project which sees the correct version of the SI jars used. Has impact on the build.gradle file"
Answer: 2785.0

User story: "Thinking about using the official SpringSource rules as a template"
Answer: 22875.0

User story: "We need to fail fast."
Answer: 37608.0

User story: "Create proper test coverage for Controllers"
Answer: 136476.0

User story: "CI job will run integration tests that are tagged for CI build."
Answer: 122373.0

User story: Since most of the xd.shell.itests will do more then one thing (deploy a stream, start it, add a tap, add a job, stop, etc) we decided to decouple writing testcases with running it. Test cases will be written in spring-shell scriptlets. Scriptlets are json files with command and expectedResult as tokens.  Here's an example:  {code} { "testscript":   [ {"command" : "stream create --definition "http | file" --name http2file",     "result" : "Created new stream 'http2file'"},    {"command" : "stream list",     "result" : "..."}  ] } {code}  A parser will parse scriptlets, executes it and asserts on expected results.   
Answer: 262911.0

User story: "Add top level utility methods to manage XD runtime (deploy, start and stop). These methods will be used by underlying integration tests to control runtime test environment.  "
Answer: 270102.0

User story: "See XD-477"
Answer: 11039.0

User story: "See XD-477"
Answer: 10675.0

User story: "See XD-477"
Answer: 10958.0

User story: "XD-482 addresses the use of camel case in 'fixed-delay' job module parameter name. and, we need to fix the same for other module parameters wherever '-' is being used. "
Answer: 123091.0

User story: We need to determine where this information could fit in. It can be either in "README" at the project home page or "Getting started" wiki page.
Answer: 3130.0

User story: "Shell command to delete a trigger.   Note: this command will only remove the trigger definition not modifying the jobs that use the trigger."
Answer: 17366.0

User story: " public StreamPlugin(){   postProcessContextPath = CHANNEL_REGISTRY;  }  Subclasses should not directly update superclass fields."
Answer: 110871.0

User story: Current behavior is to just have a prompt of "unknown:>"  I think any return value of a @CliCommand method is not shown b/c the whole infrastructure is not up at that time
Answer: 22857.0

User story: Caused by that weird annotation dependency problem that I worked around for compile. But Sonar complains.  One solution would be to add Jackson 2 to the Sonar "classpath", but I did not manage to do that.  
Answer: 12774.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: "DefaultFormattingConversionService provides Collection -> Object conversion which will produce the first item if the target type matches. Here, this results in an unfortunate side effect, getTuple(List<Tuple> list) would return a Tuple which is misleading. In this case it is preferable to treat it as an error if the argument is not a Tuple."
Answer: 1053.0

User story: "Save : Save a XYZDefinition - method used to be 'create' Delete : Delete a XYZDefinition - method used to be called 'destroy' Deploy : Deploy a XYZDefinition Undeploy : Undeploy a XYZDefinition List : List a XYZDefinition        Returns PagedResources<XYZDefinitionResource> Display : Get specific information about a XYZDefinition  Create other stories for each Controller and include in this weeks sprint "
Answer: 9987.0

User story: "Only ‘create’ in TapDeployer has some additional code to check if the stream exists, could take place in another location."
Answer: 4128.0

User story: "To be consistent with Spring Data Repository method names."
Answer: 9904.0

User story: "Favor using custom  exceptions instead of using Assert.notNull, review usage and make changes.  Eg. if a stream can't be found (or another definition) a 'XYZNotFoundException' instead of Assert.Null on the return value of a findOne method "
Answer: 5342.0

User story: "StreamController to not access the repository instance directly, all access to go through StreamDeployer "
Answer: 12993.0

User story: "Rename existing Tap class to something else."
Answer: 21227.0

User story: "See implementation used for Steams and apply to jobs, taps, triggers."
Answer: 2106.0

User story: "See implementation used for Steams and apply to jobs, taps, triggers."
Answer: 10049.0

User story: "Resource objects should be returned from all controller methods. MVC Tests should be added to check returned values."
Answer: 2922.0

User story: "We need a few steps 1. Investigate if we need to move off Spring Shell 1.0 dependency, e.g. need to use code in Spring Shell 2.0 branch 2. If we need to use code in Spring Shell 2.0 branch, we need to release a Spring Shell 1.1 M1 release with appropriate code changes.  Create stories related to Shell release. 3. Determine and document the basic recipe for doing integration tests. 4. Create stories to provide integration tests for each existing command"
Answer: 10115.0

User story: "Implements automatic conversion. Provide APIs to channel registry to register Payload conversion. Includes Redis and Rabbit transport."
Answer: 20516.0

User story: "A module can declare one ore more payload types it will accept. This will inform the runtime re. automatic payload conversion.  This can be done in the module XML configuration and processed by StreamPlugin"
Answer: 2018.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: "Spring HATEOAS is here to help. Nonetheless, there are currently a number of outstanding issues, namely:  https://github.com/SpringSource/spring-hateoas/pull/98 https://jira.springsource.org/browse/SPR-10262#comment-91685 https://github.com/SpringSource/spring-hateoas/pull/94  Creating a issue here for future reference"
Answer: 1423.0

User story: "We need a generic script that can do JSON to tab-delimited text transformation for data written to HDFS/HAWQ external tables. Users should be able to specify columns/fields to be included."
Answer: 1052629.0

User story: "we need to modify startup script to use hadoop 1.1.2 as default or phd1 when specified with --hadoopDistro=phd1"
Answer: 28473.0

User story: "we need to modify build adding two sub-projects for spring-xd-hadoop: one for hadoop 1.1.2 and one for phd1 (Pivotal HD) to pull in transitive dependencies for correct Hadoop distro"
Answer: 25277.0

User story: "we need a batching JDBC channel adapter (int-jdbc:outbound-channel-adapter is not batching statements AFAICT) "
Answer: 1246239.0

User story: "we need a JDBC sink for writing to HAWQ (using int-jdbc:outbound-channel-adapter and postgresql JDBC driver) "
Answer: 9883.0

User story: "spring-data-hadoop 1.0.1.RC1 provides flavors for commonly used Hadoop distros/versions and we should make use of that."
Answer: 7069.0

User story: There's a lifecycle problem when a tap creation fails (e.g. because the DSL syntax is wrong). Subsequent attempts to create the tap will fail with an error:   [{"links":[],"logref":"MessageHandlingException","message":"org.springframework.context.ApplicationContextException: Failed to start bean 'org.springframework.integration.monitor.IntegrationMBeanExporter#0#92e27d20-4c48-4131-866c-91b6cb642ca2'; nested exception is org.springframework.jmx.export.UnableToRegisterMBeanException: Unable to register MBean [MessageChannelMonitor: [name=nullChannel, sends=0, receives=0]] with key 'xd.tap1:type=MessageChannel,name=nullChannel,index=1,module=log'; nested exception is javax.management.InstanceAlreadyExistsException: xd.tap1:type=MessageChannel,name=nullChannel,index=1,module=log"}]  Disabling JMX solves the issue.   reproduce Create a bad stream definition name 'bad' Try to recreate with the same name, but correct stream definitions.  The system will report that the stream already exists.
Answer: 412049.0

User story: "Support toString() to emit JSON by default. Should be backed by a simple strategy to allow the possibility of other representations.  Also provide toTuple(String json). This supports seamless mapping JSON<->Tuple in XD"
Answer: 4152.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: For example, using tcpdump I can see both an exception and message information:  'HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type: application/json;charset=UTF-8 Transfer-Encoding: chunked Date: Fri, 12 Jul 2013 13:38:26 GMT Connection: close  275 [{"links":[],"logref":"MessageHandlingException","message":"org.springframework.context.ApplicationContextException: Failed to start bean 'org.springframework.integration.monitor.IntegrationMBeanExporter#0#92e27d20-4c48-4131-866c-91b6cb642ca2'; nested exception is org.springframework.jmx.export.UnableToRegisterMBeanException: Unable to register MBean [MessageChannelMonitor: [name=nullChannel, sends=0, receives=0]] with key 'xd.tap1:type=MessageChannel,name=nullChannel,index=1,module=log'; nested exception is javax.management.InstanceAlreadyExistsException: xd.tap1:type=MessageChannel,name=nullChannel,index=1,module=log"}]  However the client only shows:  http://localhost:8080:>tap create --name "tap1" --definition "<EMAIL> | log" --deploy true 14:38:26,113  WARN Spring Shell client.RestTemplate:524 - POST request for "http://localhost:8080/taps" resulted in 500 (Internal Server Error); invoking error handler Error creating tap 'tap1'  The error doesn't seem to be logged in the XD Admin server either, so the information is effectively lost.  
Answer: 9951.0

User story: "A pause means that a trigger will wait to fire its job until after the pause is removed.  It does not apply the misfire behavior. "
Answer: 757030.0

User story: "  Commonly called Calendar support "
Answer: 757034.0

User story: " In the case that there are not enough resources to fire a trigger, the highest priority will be fired first."
Answer: 757036.0

User story: "If we want spring-xd to support interactions through a UI, then it would make sense that we should support the UI coming from a separate origin.  This way, the UI could remain a separate project and be served from wherever we want.  So, we would need to add the header to *all* outgoing REST responses. We may also need to add a {{Access-Control-Allow-Methods}} header as well.  In the short term, the {{Access-Control-Allow-Origin}} header could be hard coded to a specific url (I'm using http://localhost:9889 for now), but in the long term we would need this configurable."
Answer: 26563.0

User story: "The following will retrieve the names of all module types (eg- sources, sinks, jobs, processors, triggers).   {code} GET /module-types/ {code}  I'm expecting that the plural would be used, but singular would work as well.  The following gets modules of a given type: {code} GET /module-types/{type} {code}  This would be similar to the {{/modules/}} call in XD-265, but it would only return modules of the specified type.  "
Answer: 98963.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: "2 options are: 1) Fire the trigger immediate - Launch the job when trigger can gather the resources necessary start the job 2) Do nothing - Ignore this job fire time and catch   this scenario can occur if XD is down or resources (threads) are not available at the time a job is to be launched. "
Answer: 757058.0

User story: "We need to have the ability to set read timeout for http request.  This is already implemented here: https://github.com/SpringSource/rest-shell/"
Answer: 147762.0

User story: "Dependent servers should be required on the CI server, but optional on developer systems."
Answer: 268.0

User story: "Once issues like XD-438 have been completed the wiki doc will need updates to reflect the current behaviour and syntax options."
Answer: 148253.0

User story: "With support for substreams/parameterized streams now in the parser it will be possible to create a stream that cannot be deployed: it may not fit the source/processor*/sink structure or it is a parameterized stream with no default values for parameters. Need to check how XD is going to handle these - after creating them, attempting to 'deploy' them should return appropriate errors. (They should exist in the stream directory)."
Answer: 139886.0

User story: "The new parser supports | for connecting regular modules and & for connecting job steps. The modules in the ast that were connected with & are tagged but nothing is currently using that information (it doesnt get into the module deployment request). We need to think about using this data: policing the modules that are being deployed to ensure they are job steps, for example."
Answer: 139890.0

User story: "Following stream parsing there is now a stream resolution stage that chases down substream references and fills in parameterization. The 'lookup' of streams is done through implementors of the StreamLookupEnvironment interface. Currently the parser implements this itself but it is really a job for the stream directory.  The parser implementation doesn't know about stream deletions, for example, so may still resolve streams that no longer exist."
Answer: 29750.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 DSL changes under XD-369 now build stream Ast objects that can include a source and sink channel:  {code} // Source Channel :mystream.foo > count | log  // Sink Channel http | count > :foo {code}  These new fields in the Ast object need to be copied into the module deployment request objects and then used at the destination as the channels for wiring things together.  Currently the only channels used are the .NNN numeric channels where NNN is the index of the module in the stream definition. The source/sink channels are 'extra' channels that need creating - the source channel acting as a real source for the next module in the chain whilst the sink channel acts as a sink output for the last channel in the chain.    I can think of two ways to handle the implementation: - In order to police the stream structure as "source | processor* | sink" maybe special SourceChannel and SinkChannel modules are created to represent these channels and when deployment happens the deployer understands that they don't represent a real request to deploy a module but simply the channels to wire up to the adjacent module.  - Carry source/sink channel info in the existing module definitions. But then the verification of source/processor*/sink structure will need modification to say a source isn't necessary if the first processor has a source channel attached and a sink isn't necessary if the last processor has a sink channel attached. 
Answer: 28858.0

User story: "Looking at the latest Sonar run we have 3 package tangles in Spring XD:  https://sonar.springsource.org/drilldown/measures/7717?metric=87"
Answer: 18809.0

User story: Currently spring-xd-dirt has direct dependencies on Redis and Rabbit. Consider moving transport dependent classes to separate jars with "runtime" dependencies
Answer: 718532.0

User story: "The basic launch configurations should be tested automatically to ensure that startup scripts and launch aren't broken by changes."
Answer: 295.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: "As a user, I'd like to have the option to delete the queues/topics so that we can include an _optional_ attribute as part of the stream destroy command to also clean-up the associated queues/topics.  *Notes:* * Spring-AMQP {{RabbitAdmin}} now has a {{getQueueProperties()}} method which returns the number of consumers so it may be possible to use it for this purpose. * Consider the possibility of _producers_ and/or _queues_ still containing data * Consider the scenario even after the topics/queues are cleaned-up, what to do with fanout exchange?  *Some Further Thoughts* * Consider using the upcoming Spring AMQP REST API {{RabbitManagementTemplate}} if the timing is not right, we could temporarily invoke the rabbit REST API directly. * Should be optional; perhaps via {{stream destroy foo --clean}} * Should this be done by the admin? Or, via a new plugin handling module undeployments - in the rabbit case, undeploying a consumer would check for us being the last consumer and remove the queue/binding/exchange, since we undeploy left->right, everything can be cleaned up on the consumer side. * Third option would be new methods on the bus {{cleanConsumer}} etc invoked by the {{StreamPlugin}} * Down side of doing it on the admin is that he wouldn't necessarily know which rabbit cluster a stream was deployed to - so it probably has to happen on the container - even so, we'd need the admin url(s) for the cluster."
Answer: 1049999.0

User story: "If Redis is not running, the container fails to initialize in {{ContainerMain.launch()}} because the connection factory attempts to eagerly connect.  If RabbitMQ is not running, the container fails to initialize in {{AbstractContainerLauncher.launch()}}.  Make the failure behavior consistent from a user perspective and add a spring-retry {{RetryTemplate}} to retry container startup."
Answer: 416312.0

User story: "XD-162 requires registering message converters with the ChannelRegistry. End user needs to configure this statically as the Spring configuration is not exposed."
Answer: 508532.0

User story: "Avoid the need for {{--jmxPort=xxxx}} when running both a {{Container}} and {{Admin}} on the same server"
Answer: 24489.0

User story: "See http://static.springsource.org/spring-xd/docs/1.0.x-SNAPSHOT/reference/html/#_test_the_deployed_module_3 "
Answer: 19507.0

User story: "See http://static.springsource.org/spring-xd/docs/1.0.x-SNAPSHOT/reference/html/#_test_the_deployed_module"
Answer: 19507.0

User story: """test the deployed module"" sub-section uses curl."
Answer: 19508.0

User story: "Add section to Analytics chapter on use of AggregateCounter.  The example should show the use of the shell to create the tap that uses the AggregateCounter."
Answer: 15317.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   http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#taps  The existing docs should be made to show a real stream being created with filter and/or transformer and then a tap that goes to logging.    The shell syntax to also stop/undeploy a tap should be shown here as well since the lifecycle is discussed."
Answer: 19522.0

User story: "See   http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#gemfire "
Answer: 19516.0

User story: "See   http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#tcp_sinks"
Answer: 19517.0

User story: "See   http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#hdfs"
Answer: 19518.0

User story: "See   http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#file_sinks"
Answer: 19519.0

User story: "See   http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#log_sinks"
Answer: 19519.0

User story: "See   http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#script"
Answer: 19518.0

User story: "See   http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#json-field-extractor"
Answer: 19519.0

User story: "See   http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#transform"
Answer: 19520.0

User story: "See   http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#filter http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#json-value-filter"
Answer: 19521.0

User story: "See   http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#tcp"
Answer: 19530.0

User story: "See   http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#syslog"
Answer: 19530.0

User story: "See   http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#gemfire-cq"
Answer: 19529.0

User story: "See   http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#twittersearch"
Answer: 19530.0

User story: "http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#tail"
Answer: 19530.0

User story: The documentation in the Running in Distributed Mode chapter should discuss that the distributed runtime can use essentially any middleware to communicate between nodes.  This functionality is provided by the core ChannelRegistry abstraction.  A new intro paragraph shoul convey that it isn't a 'redis' only or 'rabbitmq' only system.  There should be "Installing RabbitMQ" and "Starting RabbitMQ" sections to match those for Redis.  "Starting Spring XD in Distributed Mode" should cover how to configure the system to select to use Redis or Rabbit.
Answer: 15172.0

User story: "See http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#http    "
Answer: 3839.0

User story: "There are existing commands that can be taken from   https://github.com/SpringSource/spring-hadoop-samples  or   https://github.com/SpringSource/impala  that can be used for this"
Answer: 12925.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 current streams chapter  http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#streams  shows using curl to post some data to a http source module,   curl -d "hello" http://localhost:9000  create a shell command so curl doesn't have to be used.  https://github.com/SpringSource/rest-shell  has a command already developed for this.
Answer: 3720.0

User story: "the current streams chapter  http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#streams  shows creation and deleting streams using CURL - switch to use shell.  Also add listing of a stream.  there is also an example of creating a stream, this should be replaced as well. "
Answer: 4146.0

User story: The chapter on how to start up the shell should ocme right after "start the runtime" and before "create the stream"
Answer: 4156.0

User story: "See http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#getting-started  "
Answer: 4126.0

User story: "This section should discuss what is exposed via JMX, how you can view it in JConsole, and how you can view it over http via Jolikia.  in particular showing how some existing metrics for inbound message channel adapters or the 'inbound' channel of the stream, that indicate the number of messages processed per section.    "
Answer: 417925.0

User story: This should likely be in the "start the runtime" section of Getting Started section.
Answer: 393316.0

User story: "-New exception types are starting to appear in XD. Need to define what types of exceptions should be thrown for common scenarios. Assuming XD is all RTEs, we will wrap thrown exceptions to RTEs or defined sub types. What standards should apply?"
Answer: 1255984.0

User story: "As part of the Hadoop World demonstration work, the flow of data using XD from twitter to be analyzed by HAWQ as done.  Part of this work had the data going into HDFS that HAWQ was able to query using external tables.  The work for this story is to identify the concrete technical tasks/stories to be created do deliver and document this functionality in XD.  "
Answer: 10245.0

User story: Some (java) files are currently missing headers.  The plugin at https://github.com/hierynomus/license-gradle-plugin can help, but initial trial revealed that:  - skipExistingHeaders does not seem to be honored. We may then need to use a year construction like 2001-${current} or force all files to have ${current} year. Don't know the legal implications of this - Default source sets encompass all files "in the classpath" basically, so that means .xml as well as .properties files for example. It would seem logical to add header to those as well, but I don't think this is what we do on other projetcs.
Answer: 543304.0

User story: "Have proper exceptions for common error cases on Stream creation/deployment and propagate those to clients correctly."
Answer: 80788.0

User story: "see StreamsRepository as an example. This includes in memory and Redis implementations"
Answer: 2758.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://docs.google.com/a/gopivotal.com/drawings/d/1kCNbVspRBjGc10itF9cSkwST8WgCjgg3wGzFKqLCAzU/edit"
Answer: 2651.0

User story: "see https://docs.google.com/a/gopivotal.com/drawings/d/1kCNbVspRBjGc10itF9cSkwST8WgCjgg3wGzFKqLCAzU/edit  create TapsController if necessary"
Answer: 23.0

User story: "see https://docs.google.com/a/gopivotal.com/drawings/d/1kCNbVspRBjGc10itF9cSkwST8WgCjgg3wGzFKqLCAzU/edit  Refactor current DefaultStreamDeployer"
Answer: 9546.0

User story: "see https://docs.google.com/a/gopivotal.com/drawings/d/1kCNbVspRBjGc10itF9cSkwST8WgCjgg3wGzFKqLCAzU/edit  create optionally deploys"
Answer: 9548.0

User story: "see https://docs.google.com/a/gopivotal.com/drawings/d/1kCNbVspRBjGc10itF9cSkwST8WgCjgg3wGzFKqLCAzU/edit  Create the deployer if it doesn't exist."
Answer: 11176.0

User story: "see https://docs.google.com/a/gopivotal.com/drawings/d/1kCNbVspRBjGc10itF9cSkwST8WgCjgg3wGzFKqLCAzU/edit  Create the controller if it doesn't exist. Test with MvcTest"
Answer: 11187.0

User story: "To store it's definition and optionally deploy with --autostart flag"
Answer: 10546.0

User story: "Deploy an existing job. Must exist in the JobsRepository"
Answer: 20068.0

User story: "optional --autostart switch to also deploy the job"
Answer: 20069.0

User story: "Deploy a named stream. The stream must exist in the StreamRepository"
Answer: 9560.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: Extend the DSL in the following ways:  - stream naming, use <name>'=' {code} mystream = http | file {code}  - module aliasing (for later referencing) use <label>':' {code} mystream = http | t1: transform --expression=payload.toUpperCase() | t2: transform --expression=payload.toLowerCase() {code}  - sequence of job steps with '&' {code} mybigjobby = step1 --option=value & step2 --option=value {code}  - Channels for sources and sinks, use '>', channels references prefixed ':' {code} // sink channel called foo http | transform --expression=payload.toUppercase() > :foo // source channel called foo :foo > count | file {code}  - Qualify channels with a stream ':'<stream>'.'<channel> {code} mystream = http | transform --expression=payload.toUppercase() > :foo :mystream.foo > count | log {code}   - Reusable substreams, define then reuse {code} myIntricateFlow = transform --expression=payload.toUppercase() | transform --expression=payload.toLowercase()  http | myIntricateFlow | file {code}  - Parameterized substreams, use $XX or ${XX} to indicate parameters {code} obfuscateName = transform --expression=payload.replaceAll("${name}",XXX)  twitter --query=Bieber | obfuscateName --name=Justin | file {code}  - Tapping (still not 100% happy about the format here) {code} mystream = http | filter | t1: transform XXX | t2: transform YYY | file  // These are then equivalent (tapping on a module is effectively tapping a channel, hence the '>') tap filter > count | file tap mystream.filter > count | file  mystream = http | filter > :foo  tap :foo > count | file tap :mystream.foo > count | file {code} I'd still like to thing about removing 'tap' and using a symbol (perhaps '@', but @:mystream.foo is a little odd)  still not covered, topological constraints on the stream components.
Answer: 42909.0

User story: This is currently too chatty. It should be possible to use a single connection for each "increment" operation.
Answer: 2807.0

User story: "Get closure on open discussion points for REST API wrt to streams, taps and jobs. "
Answer: 30017.0

User story: when posting the DSL to create a spring batch job e.g. "trigger job.xml --option1=foo"  it should be stored (in redis) so that a listing of XD job definitions can be retrieved.
Answer: 10036.0

User story: "Right now the PPC for jolokia mgmt is conflicting with the PPC used to resolve redis properties.  Need to determine a strategy such that multiple PPCs can be used."
Answer: 125.0

User story: "Redis based."
Answer: 12889.0

User story: "Simple cron based triggers"
Answer: 10068.0

User story: It might be worth creating a base class for Plugins that combines common concerns across plugins. E.g. That would allow us to hide the commonApplicationContext and BeanDefinitionAddingPostProcessor for common cases, instead exposing a simple addBeanDefinition method to sub-classes."
Answer: 13021.0

User story: "startup scripts on windows should be tested, xd-admin, xd-container, xd-shell."
Answer: 293.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: "Need to understand how individual modules may or may not share Dispatchers that are part of the parent context.  If modules have their own dispatchers, those also need to be configurable."
Answer: 489739.0

User story: "- Container context should be separate from Admin Context in local mode (consistency across transports). Provide a LocalChannelRegistry to bridge deploy and undeploy channels to the ModuleDeployer  - Verify Plugins are not in common module context. They are only needed by the ModuleDeployer not the Modules.  - Add global-beans Config for beans to be shared among admin and container (and available to modules). This would be set as the parent context where needed. (Currently ‘analytics-context.xml’ and JobRepository shared by Admin and modules)  - Fix ModuleDeployer sets parentContext twice - Rename common.xml to module-common.xml  NOTE: Analytics parent only required in local mode  - Write unit tests to verify configurations are as expected. Correct bean implementations and no stray beans or redundant instances where not needed  - Decouple Command options from System properties (in general XD property names), this gives us some flexibility in mapping to properties or profiles where appropriate "
Answer: 75329.0

User story: "Currently Jobs can be either executed using cron expression or immediately at once. We should also support the one-time scheduling of jobs in the future.  Would this possibly require us to implement schedule-persistence? That could severely impact story-points."
Answer: 298582.0

User story: "Trigger - Add support for fixed-delay interval"
Answer: 9581.0