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: "The object naming is still not ideal for XD since SI conventions add some noise. Likely  need to design and implement a custom naming strategy"
Answer: 292439.0

User story: "There is some conflicting Servlet API jars on the claspath that needs cleanup. Building and running with xd-singlenode script gave this error:  Jun 27, 2013 3:18:16 PM org.apache.coyote.http11.AbstractHttp11Processor process SEVERE: Error processing request java.lang.NoSuchMethodError: javax.servlet.ServletContext.getEffectiveSessionTrackingModes()Ljava/util/Set;  at org.apache.catalina.connector.CoyoteAdapter.postParseRequest(CoyoteAdapter.java:674)  at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:402)  at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)  at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)  at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310)  at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)  at java.lang.Thread.run(Thread.java:680) "
Answer: 70.0

User story: "Document jmx command line options and refer to jolokia"
Answer: 434339.0

User story: "We should be able to write a script that can examine the table structure for a given HAWQ table and then extract the data from JSON without the custom script we are using now."
Answer: 1075527.0

User story: "Investigate how efficiently we can integrate profiler into the performance test."
Answer: 6747.0

User story: "Create a load generator script which can generate messages at specific  1) Rate 2) Payload 3) Concurrency  to a specific tcp/udp port where a syslog adapter is listening."
Answer: 1069796.0

User story: updated story points to 14 since 5 of us just participated in a 2 hour call, and we still need to discuss "topology" support after some dev spikes later this week
Answer: 4289.0

User story: "TODO as part of this (see XD-537):   * Get rid of so-called Service layer in analytics project (doesn't do much right now, and logic would better live in the 'Handler' IMO) * Have REST controllers depend on XRepository in all cases"
Answer: 51922.0

User story: "TODO as part of this (see XD-537):   * Get rid of so-called Service layer in analytics project (doesn't do much right now, and logic would better live in the 'Handler' IMO) * Have REST controllers depend on XRepository in all cases"
Answer: 50001.0

User story: "TODO as part of this (see XD-537):   * Get rid of so-called Service layer in analytics project (doesn't do much right now, and logic would better live in the 'Handler' IMO) * Have REST controllers depend on XRepository in all cases"
Answer: 45008.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: "TODO as part of this (see XD-537):   * Get rid of so-called Service layer in analytics project (doesn't do much right now, and logic would better live in the 'Handler' IMO) * Have REST controllers depend on XRepository in all cases"
Answer: 48520.0

User story: "For a sink/source/processor this would be (among other things) message rate, number of messages"
Answer: 306614.0

User story: "POST?"
Answer: 14766.0

User story: "This would be based off the spring-integration-extenstions splunk project.  The use of this adapter for storing tweet data is in https://github.com/markpollack/springone  We should be able to reproduce the use case as done in that demo"
Answer: 4573.0

User story: "Need to capture exceptions from the various projects that make up XD and wrap them in XD Specific exceptions.  An example of this is when leaving out the channels in the module definitions, we see NoSuchBeanExceptions and IllegalArgumentExceptions thrown based on which module and what channel is missing. "
Answer: 155235.0

User story: "The shell should be an 'executable' delivered out of the box in much the same way that xd-container and xd-admin are right now. If we follow how redis/mongo distribut the shell, it sits side by side with the other binaries"
Answer: 8804.0

User story: "Expose runtime stats for core components."
Answer: 498675.0

User story: "Global option?  Override for individual modules? module types?"
Answer: 4452.0

User story: "WAR Vs. JVM Jolokia Agent  Jolokia Vs. JVM MBeanServer  Probably needs support for Spring Profiles."
Answer: 4460.0

User story: "Probably needs support for Spring Profiles."
Answer: 9169.0

User story: "See XD-194 for additional considerations. Zip support should be similar to uber-jar, or possibly replace uber-jar support."
Answer: 307945.0

User story: Examples: 1. Be able to start the rabbitmq source just by pointing to modules/source/rabbit.xml, pass in some property file for parameters to be replaced, and outgoing message is placed in a in-memory queue backed channel for use with assertions to verify functionality.   2. Test for as many source types as is 'reasonable', e.g. MQTT/TCP testing might be harder than say rabbitmq. 3. Test that sending json, results in media-type header is set to json 4. Test that sending POJO,   "  POJO 5. Test that sending Tuple, "   Tuple 6. Test that sending raw bytes, " raw bytes 
Answer: 336665.0

User story: "Handled by 1245"
Answer: 352425.0

User story: "Be able to point to the processor xml file, e.g. modules/processors/transformer.xml, and have access to a source channel that drives messages into the processor and a output channel where output messages are send.  The outbound channel is queue backed.  Test sending JSON to a processor module that uses Tuples. "
Answer: 352425.0

User story: "So that we can validate the message content in the stream"
Answer: 497908.0

User story: "To send a pre-set message to process(es)"
Answer: 352445.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: "It would be nice if we have a git repo for Spring XD performance testing.  This would enable us to have a common repository (rather than inside spring-xd as a subproject) for all performance related code specific to any module, message middleware etc.,  "
Answer: 3331.0

User story: Twitter's streaming APIs have more capabilities than just the plain statuses/sample.json. In particular we should support the filter.json option and the use of "track" (https://dev.twitter.com/docs/streaming-apis/parameters#track) as well as other request parameters (delimited, language etc).
Answer: 9941.0

User story: "I wanted to have a rollover feature when I was streaming tweets to a file overnight, just to avoid dealing with a single enormous file (in case I collected more data than my demo could handle and needed to split it up)."
Answer: 1075971.0

User story: "The changes for XD-144 mean that log4j files are no longer in the library jars. The admin server already has a logging configuration which should be activated by the startup scripts, but the separate gemfire app doesn't."
Answer: 8752.0

User story: "Currently, the RedisQueueInboundChannelAdapter has blocking operation when pulling the messages out of redis queue and this is not performant.   There are few ideas from the discussion to make it better:  1) Get more items from the redis queue per connection 2) We will also have compression of messages(at the channel registry) before being sent to the redis queue   We also need to investigate what redis connection strategy makes the RedisQueueInboundAdapter better. "
Answer: 506988.0

User story: "See https://github.com/kevinweil/elephant-bird"
Answer: 1078905.0

User story: "See https://github.com/kevinweil/elephant-bird"
Answer: 1078905.0

User story: "the key used in writing key-value pairs should be able to be specified declaratively."
Answer: 322754.0

User story: "Writing POJOs using CDK Data (Avro)  We should support both partitioned and un-partitioned.  This story addresses only un-partitioned.  Document limitations in terms of which Java types are supported and not supported by the Avro serialization "
Answer: 199101.0

User story: "This could be an optimization, to be verified, that delegating the writing operations to Reactor (e.g. with a backing ringbuffer implementation) will increase the throughput performance.  Other strategies, such as threads to handle writes to individual files concurrently, should be investigated."
Answer: 1078922.0

User story: "This should be an optimization, to be verified, that aggregating data in memory, for example at the size of a HDFS block (64Mb often) will result in increased performance vs. not aggregating data for writes."
Answer: 1078922.0

User story: "Based on message processing, a header in a Message can be added that contains the output file name.  This will work together with the hdfs writer module so it can read the header and write the contents of the message to the specified file. "
Answer: 1078923.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 file name should allow the use of date and time patterns, either JDK or Joda (TBD)."
Answer: 1078924.0

User story: "A strategy that will automaticaly roll over files based time of day.  For example  New files will be created every hour, or every 6 hours etc.  The directory for files can also be rotated so that directory structures such as  /data/{year}/{month}/{day}  can easily be supported with a minimum of configuration.  "
Answer: 1078927.0

User story: "A strategy to roll over files that allows the user to choose between  1) the size of the file 2) the number of events/items in the file 3) an idle timeout value that if exceeded, will close the file"
Answer: 322755.0

User story: "A file that is in the process of being written to should have a customized suffix added to the name, e.g. 'temp'.  Once the file is closed, the suffix is removed and replaced with another value - default value can be dependent on the serialization format used, but can be customized"
Answer: 322731.0

User story: "h2. Narrative As XD, I need a persistent way to register job definitions (beyond the map registry implementation provided by Spring Batch).    h2.  Acceptance Criteria # XD should be able to register, unregister, and find job definitions via the registry. # The registry should be backed by Redis so that it is persistent."
Answer: 37332.0

User story: "Command line arguments (and especially their default values) are currently scattered around different places.  The aim is to regroup those in a common place (*Options classes make sense).  Also, not very happy with how System properties are used as a vehicle for options.transport / options.home"
Answer: 1950.0

User story: "h2. Narrative As an XD developer, I need to be able to use a batch job to stream data as a source.  h2.  Acceptance Criteria # Implement the ability for a job to be defined as a source in the DSL # Add the configurations for the batch infrastructure transparently to the user # Add the ability to specify if the job is stateful (picks up where it left off if it stops or restarts at the beginning)."
Answer: 179404.0

User story: So that clients (e.g. Shell or custom user program) are insulated from REST details (ala Cloud Foundry).  May go even further if we want a Java DSL for stream definitions (that may reuse Batch command POJOs btw): Difference between: xdClient.createStream("mystream", "http --port=9000 | file") and  import static stuff.*;  StreamDef stream = http().port(9000).pipe(file()); xdClient.createStream("mystream", stream);
Answer: 4070.0

User story: "GET /streams/{streamname}/modules    and GET /streams/{streamname}/modules/{modulename}  The former returning links to the latter "
Answer: 132469.0

User story: "Pagination support, maybe querying by name as well"
Answer: 20541.0

User story: "This is the basic setup of the commands file - no specific command implementations"
Answer: 12690.0

User story: "Set up a basic Spring Shell project for XD Shell"
Answer: 12693.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 stream creation we need to be able to specify:  source sink processor  - filter  - transformer  - script  etc. "
Answer: 13044.0

User story: "Need to create a basic client library to provide easier access to the XD REST API. "
Answer: 13050.0

User story: "Need to create a basic Spring Shell implementation to provide easier access to the XD REST API via an XD REST API Client library. "
Answer: 11626.0

User story: "Running on Cloud Foundry (and other managed environments) we need to be able to specify a Redis password in addition to host and port."
Answer: 20543.0

User story: "h2. Narrative As a user of XD, I want to be able to use a job as a source.  To do so, we need the output of a job to be written to a message channel  h2.  Acceptance Criteria # Create a new ItemWriter in the Spring Batch project to write to a Spring Integration message channel."
Answer: 181219.0

User story: h2. Narrative As a developer, I need a way to deploy job configurations as well as the related custom code to XD.  h2.  Acceptance Criteria # Provide the ability to register jobs that have been deployed as modules via something like {{curl -d "job" http://localhost:8080/streams/myJob}} where job is the name of the job definition located in /modules/job and myJob is the name of the resulting registered job # Confirm that both "regular" jobs and Spring Hadoop based jobs can be packaged/run.
Answer: 12817.0

User story: "h2. Narrative As the XD system, I need to be able to execute a job (or potentially a stream) based on a given condition (time, data existence, etc).  This story is intended is for a local trigger implementation but remote triggers will also need to exist.  h2.  Acceptance Criteria # Implement the ability to register a time based trigger {{trigger <CRON_STRING>}} for example # Implement the ability to register a file existence based trigger {{trigger <PATH>}} for example # Implement the ability to execute a job via an anonymous trigger: {{job_name @ <CRON_STRING OR PATH>}} # Implement the ability to execute a job via a job via the previously registered trigger: {{job_name @ trigger_name}} "
Answer: 21381.0

User story: "An aggregate counter rolls up counts into discrete time buckets.  There is an existing POC implementation in Java based off the library https://github.com/thheller/timed-counter   The README there has a good description of the desired feature set."
Answer: 20079.0

User story: "we have a prototype gardenhose adapter that was built directly upon RestTemplate (streaming on a background thread), but Spring Social Twitter has an issue on its 1.1 roadmap that is relevant: https://jira.springsource.org/browse/SOCIALTW-2 "
Answer: 4428.0

User story: "configurable parameters should include the queue-name(s) and optional binding key pattern  connection info, such as host and port, should also be configurable but with defaults (localhost and default port), and that should likely fallback to a rabbit.properties file in the $XD_HOME/config directory"
Answer: 2655.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 is needed for the use of the webhdfs:// scheme to talk to HDFS over http."
Answer: 45083.0

User story: We need to cleanup some of the duplicate gradle tasks that bundle spring-xd distributions.   Currently, distXD does the copy of distributions from "spring-xd-dirt", "redis" and "spring-xd-gemfire-server" projects into "$rootDir/dist/spring-xd".  And, the task "zipXD" makes the zip archive.  These tasks should be combined with the "distZip" & "docZip" tasks.  We also need to remove the duplicate artifacts configuration from these tasks.
Answer: 17877.0

User story: for example, when using the 'twittersearch' source module, the "hashTags" are nested within "entities", and the value for hashTags is itself an object with a "text" field, so the following would be needed to count the actual value of interest:  {code} tap @ tweets | field-value-counter --fieldName=entities.hashTags.text {code} 
Answer: 65.0

User story: "https://github.com/SpringSource/spring-xd/wiki/Creating-a-Source-Module uses the SI twittersearch inbound channel adapter, which is no longer going to work once Twitter disallows anonymous searches.   Ideally we update the example to use a new version of SI-twitter that adds support for this (as opposed to the XD workaround.)"
Answer: 351.0

User story: "curl -X DELETE http://localhost:8080/streams/ticktock"
Answer: 1039.0

User story: The issue arises because the link:document[Label] asciidoc macro is meant for "external documents" and creates {{<ulink>}} in docbook / {{<a href="document">}} in html, whereas we want {{<link linkend="anchor">}} / {{<a href="doc#anchor>}} resp. We also want it to continue working in github live view.  I guess what could work is to have the macro (either override the link macro or create our own if github supports that) that looks like : {{link:document#anchor[Label]}}  (the #anchor works out of the box in asciidoc and should work in github) but override it for the html and docbook backends to render to the correct form.  The thing is, there are several ways to create/override macros (and templates they render to), some of which make sense to our setup: - having asciidoc.conf in the directory of the processed document (http://asciidoc.org/userguide.html#X27) - having docbook.conf/html.conf in the directory of the processed document (http://asciidoc.org/userguide.html#X27) - defining macros using attributes (http://asciidoc.org/userguide.html#_setting_configuration_entries)  I tried all of those, but to no avail. These DO WORK with plain asciidoc, but not with our toolchain. Don't know if the problem is with asciidocTOR or with the gradle wrapper though.    
Answer: 1312.0

User story: "Those property keys should then be provided as defaults for the placeholders in source/twittersearch.xml"
Answer: 141.0

User story: "The transform, filter, and script processor modules support passing in a properties-location for script variables. We need a default location on the classpath for users to provide custom properties files."
Answer: 22.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: "Since the changes for XD-202, twittersearch requires authentication. Need to update the docs to reflect this."
Answer: 1047.0

User story: "The asciidoc wiki should have a section (included in the _Sidebar.asciidoc as well) that describes the general usage of the DSL syntax."
Answer: 195056.0

User story: "There shouldn't be a need to do a mkdir -p before sending data to a file sink."
Answer: 15251.0

User story: "The wiki docs on creating custom modules have entire build.gradle files in them. Would be good to explore existing STS templates, maven archetypes, etc or create new ones for authoring custom modules."
Answer: 237871.0

User story: The config file modules/sink/hdfs.xml has a hardcoded value to locate the namenode.   <hdp:configuration register-url-handler="false">   fs.default.name=hdfs://localhost:9000  </hdp:configuration>  the fs.default.name proprety should be configurable and we should also support loading an external configuration file using      <hdp:configuration properties-location="${xd.home}/config/hadoop.properties">     </hdp:configuration>  
Answer: 5248.0

User story: Filter, Transform, and Script modules all assume the provided script is written in Groovy.   This is partly due to the fact that the "lang" attribute of <int-script:script> can't be set to a property value (i.e. lang="${lang:groovy}"), which would allow users to pass in the expected language. Or perhaps we could use a SPEL expression or script to pick the language based on the file extension?
Answer: 1097206.0

User story: "Fill in https://github.com/SpringSource/spring-xd/wiki/Processors"
Answer: 548.0

User story: "I don't see that we have automated tests for the modules we provide out-of-the-box.  We could make the modules folder an Eclipse project (which would also help solve XD-198) and add some integration tests similar to those documented here:  https://github.com/SpringSource/spring-xd/wiki/Creating-Custom-Modules"
Answer: 323282.0

User story: This will enable arbitrary processing logic to be used in a processing step.  See http://blog.springsource.org/2011/12/08/spring-integration-scripting-support-part-1/  <int:service-activator ...>   <script:script lang="groovy" location="file:scripts/groovy/myscript.groovy"> </int:service-activator>  would be the essence of the module.  Probably 'lang' gets detected from the file extension.
Answer: 1968.0

User story: "Replace the existing DSL parser that uses string indexing with a more robust one based on a derivative of SpEL.  This will provide a stable base on which to quickly iterate on syntax. "
Answer: 2469.0

User story: "When running in local mode (no Redis) {{time | tcp}} no longer works.  Change the {{time}} source to emit the date as a String, while allowing an option to emit a {{Date}} object."
Answer: 139.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: "If a user needs to deploy a module containing custom code, they have to build a jar for the lib dir and somehow deploy the app context file separately to a modules dir.  This is a bit inconvenient to build from a project, since context files in src/main/resources typically get built into a jar.  Might be better to accept both jar and xml files in the modules dir, though that brings up the issue of classpath isolation."
Answer: 122167.0

User story: "Currently internal config files are in META-INF/spring with fairly generic names. To avoid potential collisions if users add their own configuration in the classpath, we should have a more unique location, e.g. META-INF/spring/xd"
Answer: 7084.0

User story: "With the new option of starting without requiring redis, the getting started documentation should reflect this easier way to start processing data."
Answer: 3623.0

User story: "XD-106 included detailed logging about the Redis metadata within the RedisContainerListener, but it seems as though that info could be logged somewhere closer to the establishment of a Redis connection for the XD runtime (and could be logged even if this listener, whose main role is to capture Container-related events, is not enabled)."
Answer: 30247.0

User story: "a stream such as time | filter --script=oddMinuteFilter.groovy | file   would load the groovy script 'oddMinuteFilter.groovy' that is located in the directory modules/processor or perhaps in modules/processor/scripts.  Not sure the benefit of having a subdirectory below processor just for scripts."
Answer: 994.0

User story: "This script will launch XD admin along with the module container.  As part of this implementation, we will also remove the embedded options for XD admin & container scripts."
Answer: 3840.0

User story: "Create StreamDeployer that does not depend on an adapter implementation"
Answer: 4034.0

User story: "The current StreamServer depends on RedisStreamDeployer. Call this RedisStreamServer and extract interface to allow alternate implementations"
Answer: 4037.0

User story: "The redis specific beans that are defined in the current launcher.xml should move into this configuration file.   "
Answer: 4065.0

User story: "launcher.xml can make use of the system property xd.pipeProtocol inside an import statement.  This determines which version of the XD infrastructure to load, for example what ChannelRegistry implementation, Local or Redis based, or specific message listener containers.   File name conventions should be used, so if the option passed in from the command line is --pipeProtocol localChannel  then the XML filename looked for has the 'Protocol' suffix applied, e.g. localChannelProtocol, and is loaded via the classpath.  Redis and Local will not be the only options, other implementations will be provided in the future, e.g. Rabbit, and the user may be able to provide their own implementations of these infrastructure classes (an advanced task).  "
Answer: 4066.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 name 'pipeProtocol' is tentative.    1. The command line scripts for xd-admin and xd-container would support a --pipeProtocol option, with the default being to use Redis.  (Otherwise use xd-singlenode). 2. The xd-admin and xd-container scripts will use the value of pipeProtocol to set the java system property xd.pipeProtocol when launching the app. "
Answer: 4070.0

User story: "The xd-singlenode script will launch a main application that creates both the admin node (to process http admin requests) and the container node (to execute modules for data processing) within in the same process   the xd-admin script will launch a main application that creates only the admin node (remove current embeddedContainer options)  the xd-container script will launch a main application that creates only the container node (as it is now)"
Answer: 4076.0

User story: "The current incrementAndGet approach based off redis will not easily be applicable in local model deployment"
Answer: 26.0

User story: This could easily be supported in the existing gauge by adding a setAlpha method to RichGaugeService and adding the extra parameter "alpha" to the gauge data (https://en.wikipedia.org/wiki/Exponential_moving_average). If not set it would default to the current behaviour (simple mean), otherwise it would calculate the exponential moving average in place of the mean.
Answer: 21667.0

User story: "2-3 containers (separate processes) that the stream: syslog | tcp  1 container (separate process) that aggregates the data sent from those conainers, tcp | severityFilter | hdfs       "
Answer: 11653.0

User story: "The use case is to write custom code that does processing on a specific domain class (perhaps from twitter adapter) or a tuple.  Need to package up this code so that it can be used inside XD. "
Answer: 10054.0

User story: "Document how to take an existing input/output channel adapters in spring integration and add them as a XD source/sink module.  Should be as end-user focused, step by step guide as possible.  Consider including a getting started gradle/pom.xml "
Answer: 3134.0

User story: "bottom home page - list of projects data/integration category landing pages - related projects. "
Answer: 11469.0

User story: "A minimal project page of a 'top level project' page that has basic information of docs and links to the github wiki page.  No need to list maven coordinates."
Answer: 6058.0

User story: "Add more structure, more easily find the reference guide.  The style that is here  https://github.com/snowplow/snowplow/wiki is nice. "
Answer: 6121.0

User story: "Trying to run XD offline results in an error in redis.xml because the cloudfoundry schema file is missing.  We need to add the cf-runtime jar to the classpath to resolve this."
Answer: 652.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: We need to have the XD container & admin reading the registry specific property based on the registry type selected.   From Mark F, on one of the code review comments:  Maybe rather than having redis, rabbit, etc. properties all within a container.properties we should rely upon naming conventions instead. Specifically, we could have a single configurable property for the type of channel registry ("redis", "rabbit", or "local" being possible values), and then we could use something like:  <import resource="config/${registry.type}.xml"/>  <context:property-placeholder location="config/${registry.type}.properties"/>
Answer: 6830.0

User story: "Validate that modules have required channels declared according to their type.  Currently the stream deployer accepts processors with no input, but the stream doesn't complete. We should fail earlier and more loudly."
Answer: 35984.0

User story: "example:  {code} a | (b | c) | d {code}  ...where b and c modules are deployed together as a composite module.  There are 2 options (maybe more) for how we could handle that. One would be defining a CompositeModule type that simply bridges the channels (b's output to c's input in this example). The second option would be to deploy those together on the same node as modules but using the LocalChannelRegistry between them. "
Answer: 217295.0

User story: "The conversion should be based on content-type headers, similar to the way Spring's HttpMessageConverters work (with mime types).  Also, the map of available converters should be extensible while including the most common defaults (for JSON, XML, etc). We most likely want to add a few of our own content types also (e.g. for Tuples).  Most likely, this logic and the configuration methods for extending the converter map, belong in AbstractChannelRegistry since it should be common across all implementations (i.e. the logic should be the same regardless of the transport used after-serialization/before-deserialization)."
Answer: 74912.0

User story: "The wiki repo contains a script, gen-docs.sh, that we are planning to use to generate a pretty HTML version of the Getting Started guide.   We should consider using maven (or gradle, but there is currently an issue documented in build.gradle) to generate this and other reference docs and publish them automatically as part of a nightly build."
Answer: 28681.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: "Parameter parsing does not work if an argument contains '--'.  For example:  {code} ... | transform --expression=42 | transform --expression=--payload |... {code}  Also, I was surprised that this worked..  {code} | transform --expression=new StringBuilder(payload).reverse() | {code}  ... but this didn't...  {code} | transform --expression='new StringBuilder(payload).reverse()' | {code}  I think we need to tokenize the argument (with ' if contains spaces) and remove any surrounding '...' from the result. This means if someone wants a SpEL literal they would have to use something like   {code}--expression=''Hello, world!''{code}  resulting in a SpEL literal 'Hello, world!'"
Answer: 371069.0

User story: "This will allow for a simple way to shutdown the server via an HTTP call.  Support for security is a separate story. The end goal is to have some shell scripts distributed that can issue HTTP requests to shutdown the xd-admin and xd-container servers.  The newest version of Jolokia has the ability to boostrap itself inside an application context vs. requiring a java agent.  I suspect using the application context approach will provide us with more flexibility (e.g. property replacement etc) but not sure."
Answer: 420334.0

User story: "In both cases there are multiple application contexts that can be running in the process.  The JMX Managed bean should call 'close' on those application contexts.  The more detailed lifecycle of cleanly shutting down components within those application contexts is another story."
Answer: 433130.0

User story: "We would like to have Redis driven from a config property file under XD_HOME."
Answer: 198.0

User story: "A processor module that accepts either the location of a groovy script resource or an inline script (string). Also some discussion about a default classpath location for scripts. "
Answer: 6403.0

User story: "Shouldn't we have something like a ContextRefreshedEvent Listener and output some informational messages to the console, so the user knows the Container is up (Which contexts. Maybe even print a link to the docs))? Maybe even some simple ascii art (for demos)? Right now it looks somewhat barren.  Redis provides something similar.  This may even go hand in hand to provided a better configuration model (storing common config parameters centrally)   {code}    _____            _              __   _______     / ____|          (_)             \ \ / /  __ \   | (___  _ __  _ __ _ _ __   __ _   \ V /| |  | |   \___ \| '_ \| '__| | '_ \ / _` |   > < | |  | |   ____) | |_) | |  | | | | | (_| |  / . \| |__| |  |_____/| .__/|_|  |_|_| |_|\__, | /_/ \_\_____/          | |                  __/ |                        |_|  v1.0.0.M1      |___/   eXtreme Data  Using Redis at localhost:6379     The Server (PID: 12345) is now ready on http://myserver:123/streams  Documentation: https://github.com/SpringSource/spring-xd/wiki         {code}"
Answer: 76045.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 config for simple gauge plus message handler to process message. There is some code common to RichGaugeHandler to coerce the payload to a double that should be refactored for reuse."
Answer: 4425.0

User story: "Spring config for rich gauge plus message handler to coerce a numeric or string payload to a double."
Answer: 65.0

User story: "Presently, Spring XD does not ship Windows binaries for Redis. However, Microsoft is actively working [1] on supporting Redis on Windows. You can download Windows Redis binaries from:  https://github.com/MSOpenTech/redis/tree/2.6/bin/release   [1] http://blogs.msdn.com/b/interoperability/archive/2013/04/22/redis-on-windows-stable-and-reliable.aspx"
Answer: 321498.0

User story: "Currently, Bamboo's gradle artifactory plugin has the artifacts configured to projects target(build) directory 'archives'. We need to have a way to set the final distribution archive as one of the gradle 'configurations' in our build.gradle and refer it inside bamboo artifacts."
Answer: 8213.0

User story: "Publishing an html version of the guide that uses the 'toc2' style format, table of contents on the left.  Looks like a 'stylesheet factory' http://asciidoctor.org/docs/produce-custom-themes-using-asciidoctor-stylesheet-factory/  needs to be installed.  From the theme showcase, http://themes.asciidoctor.org/preview/, the 'golo' theme has a toc2 style.  In the root of the git repo for the wiki is a build.gradle file that uses the asciidoctor gradle plugin, but it doesn't support using a single file with import as input. (See See https://github.com/asciidoctor/asciidoctor-gradle-plugin/issues/15 )  The mvn plugin does support this, so maybe using mvn is an option or just a bash script."
Answer: 1137.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 redis project uses application plugin to bundle distribution. This also includes 'java plugin' which causes java specific build behavior on this project. We should try removing the use of application plugin and use something similar or custom tasks that does the bundling. "
Answer: 290.0

User story: "The TCP source supports inbound binary data. We currently have to go through unnecessary byte[]->String->byte[] conversion."
Answer: 73495.0

User story: "If, say, xd-dirt is ahead of a local config on the classpath, it's log4j.properties is found first."
Answer: 32998.0

User story: "We need to have an externalized property file(under xd/conf/) for the xd-container & admin scripts to use as options. "
Answer: 11120.0

User story: "The {{ModuleDeployer}} calls {{getBeansOfType}} before the context has had its {{PropertySourcesPlaceholderConfigurer}} attached. This can cause issues with {{FactoryBean}} s with placeholders in constructor args because the unresolved placeholder is used when the {{FactoryBean}} is pre-instantiated to determine the type of object it will serve up."
Answer: 36155.0

User story: "Currently, the install-redis script uses relative path to determine redis source  dist file. Since this is error prone, we need to fix it."
Answer: 14343.0

User story: "The syslog source currently is hard-coded to use udp on port 11111.  Need to parameterize the port and provide an option to use TCP."
Answer: 237.0

User story: "Building XD should not be part of the out first out of the box experience, but we should include some instructions on what targets are available, such as distXD."
Answer: 173.0

User story: "Pointers to other documentation on how to install hadoop. "
Answer: 2892.0

User story: "Show overall flow of data in a stream, the server components 'admin' and 'container'.  How modules are deployed."
Answer: 12309.0

User story: "Asciidoc/doctor might have one as part of it toolchain"
Answer: 2897.0

User story: "Similar to what would show up on structure101 reports."
Answer: 123.0

User story: "To allow for groups of beans to be defined or not in the container that runs a module.  When deploying a stream (e.g. via the REST API), it should be possible to also provide profile names. Then those would apply to any modules within that particular stream deployment."
Answer: 139401.0

User story: "Based off SI tcp inbound adapter.  This will allow for event fowarding."
Answer: 3346.0

User story: "Based off SI tcp inbound adapter.  This will allow for event forwarding that can select among the existing SI serialized/deserializer options. "
Answer: 2290.0

User story: "This will eventually be supplied by the admin server, but for now write it up by hand in the documentation"
Answer: 11610.0

User story: "Need to shutdown cleanly, no exception messages are shown.  Order of components in the stream should be shut down from 'first to last'  (opposite of creation)"
Answer: 3198.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 default is hdfs://localhost:9000 but most new distributions/installs use 8020"
Answer: 80341.0

User story: "This should facilitate testing while avoiding any class dependencies. Also, log is a generally useful sink by itself and time is a more interesting source for testing (should accept --interval for the seconds between time messages)."
Answer: 22.0

User story: "This will enable the use of groovy scripts within modules."
Answer: 9.0

User story: "It should provide an 'expression' param for SpEL and have a default value of true (accept everything)."
Answer: 16.0

User story: "It should provide an 'expression' param for SpEL and have a default pass-thru of the payload."
Answer: 17.0

User story: "The final directory structure should look like  <install-dir>/xd <install-dir>/redis <install-dir>/gemfire  inside the XD directory   /xd/bin - which has xd-container and xd-admin scripts /xd/lib  inside the gemfire directory /gemfire/bin - has the gemfire-server script /gemfire/lib   inside the redis directory is   /redis/redis-latest-v.x.y.z.tar /redis/README /readis/install-redis  - script that does the basic 4 commands to install redis.   There should be a gradle task that runs after the distZip task, that will take the contents of different project directories, script diretories and 'redis-binary' directories and creates the final layout for the distribution."
Answer: 1668.0

User story: "This is in the AdminMain and ContainerMain.    Can get the environment property directly in java code unless provided explicitly on the command line using --xdHomeDir."
Answer: 10314.0

User story: "We are packaging separate scripts to start XDAdmin and XDContainer.  The Gradle application plugin will generate an unwanted 'spring-xd-dirt' scripts, this should be removed from the bin directory when creating a distribution zip."
Answer: 2169.0

User story: "A ctrl-c of xd-admin results in exception messages about disconnecting from redis.  14:16:07,327 ERROR task-scheduler-1 handler.LoggingHandler:136 - org.springframework.data.redis.RedisSystemException: Redis command interrupted; nested exception is com.lambdaworks.redis.RedisCommandInterruptedException: Command interrupted "
Answer: 10794.0

User story: "$ ./xd-container  processing module 'Module [name=file, type=sink]' from group 'tailtest' with index: 1 processing module 'Module [name=tail, type=source]' from group 'tailtest' with index: 0   Logging of 'processing module' should have log level, time.."
Answer: 17870.0

User story: "should contain apache licence"
Answer: 2261.0

User story: "should explain basic layout of the distribution"
Answer: 2262.0

User story: "This will launch the RedisContainerLauncher, in future will be able to select from a variety of middleware options."
Answer: 113.0

User story: "Provide optional command line arg to embed the container launcher, aka - xd-admin server.    XDContainer.sh --embeddAdmin"
Answer: 115.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 Tuple classes in Reactor follow the more traditional data structure concept of Tuples, an immutable fixed length sequence of values where each value can have different types.  They are ordered and can often be access by index.  An example in a static language is the Tuple class found in .NET http://msdn.microsoft.com/en-us/library/system.tuple.aspx or in Scala http://www.tutorialspoint.com/scala/scala_tuples.htm  Using this standard definition of a Tuple, they do not support named values.  There is also a different tuple class instance for each length, e.g. Tuple<T1,T2>, Tuple<T1,T2,T3>.  The Tuple class in XD is more like a record or named tuple.   Python has a named tuple concept - http://docs.python.org/2/library/collections.html#collections.namedtuple  and http://stackoverflow.com/questions/1490413/languages-that-allow-named-tuples shows that other languages use the term 'Record' for a 'named tuple' - Haskell, Standard ML, OCaml, and F#.  http://en.wikibooks.org/wiki/F_Sharp_Programming/Tuples_and_Records#Defining_Records  So boiling it all down, to avoid conflicts of names, and also to open up the possibility of using Reactor tuples as keys (instead of strings for names), we should change the name to either NamedTuple or Record.  ATM, there is no direct relationship between Reactor's Tuple and NamedTuple (such as inheritance) and so probably Record is the way to go.   "
Answer: 347043.0

User story: "https://build.springsource.org/browse/XD-SONAR-34  Caused by: java.lang.ClassNotFoundException: org.sonar.api.Plugin         at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)         at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244)         at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230)         ... 94 more"
Answer: 605.0

User story: "For people who are familiar with Spring/Spring Integration provide documents that show how to add additional input sources/sinks."
Answer: 9767.0

User story: "Put on the guide as a section in an 'input-stream' wiki page.   "
Answer: 10133.0

User story: "Put on the guide as a section in an 'input-stream' wiki page.   "
Answer: 15799.0

User story: "Put on the guide as a section in an 'input-stream' wiki page.   "
Answer: 24349.0

User story: "Put on the guide as a section in an 'input-stream' wiki page.   "
Answer: 11404.0

User story: "Put on the guide as a section in an 'input-stream' wiki page.   "
Answer: 24338.0

User story: "Put on the guide as a section in an 'input-stream' wiki page.   "
Answer: 5985.0

User story: "Put on the guide as a section in an 'input-stream' wiki page.   "
Answer: 10134.0

User story: "Put on the guide as a section in an 'input-stream' wiki page.   "
Answer: 10134.0

User story: "Put on the guide as a section in an 'input-stream' wiki page.   "
Answer: 15795.0

User story: "Put on the guide as a section in an 'input-stream' wiki page.   "
Answer: 3127.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: "Put on the guide as a section in an 'input-stream' wiki page.   "
Answer: 11850.0

User story: "Put on the guide as a section in an 'input-stream' wiki page.   "
Answer: 11423.0

User story: "Put on the guide as a section in an 'streams' wiki page.  End user focused, no need to mention spring underpinning, impl details.  "
Answer: 11325.0

User story: "Put on the guide as a section in an 'input sources' wiki page.  https://github.com/springsource/spring-xd/wiki/GuideGettingStarted  "
Answer: 4178.0

User story: "in additional to existing tests that check for redis connection, we need to add tests that start/stop stream server. "
Answer: 325.0

User story: "stream should be able to ingest data from http "
Answer: 6014.0

User story: "The Java UUID class is known not to be the fasted implementation available.   See https://github.com/stephenc/eaio-uuid and http://mvnrepository.com/artifact/com.eaio.uuid/uuid for high perf impls.  "
Answer: 268271.0

User story: "Adopt Asciidoc as the markdown syntax, useful for generating pdf and more feature rich than standard github flavored markdown.  Loosely following the conventions of https://community.jboss.org/wiki/TheHolyGrailAsciiDocOnGitHubToDocBookTrain that have generate docbook/pdf docs from the Asciidoc wiki.  The asciidoctor project is a key element in the adoption of AsciiDoc for use as the format in github, it is the rendering engine used by github for AsciiDoc.  See http://asciidoctor.org/docs/asciidoc-writers-guide/ for guidance.  "
Answer: 7.0

User story: "Based on a single process Spring Batch job, ETL of data from HDFS to MongoDB."
Answer: 352780.0

User story: "Based on a single process running a Spring Batch job, support the ETL of data from HDFS to a RDBMS"
Answer: 352753.0

User story: "- Host the Spring XD distributable zip somewhere that is accessible by external http request. - Create brew formula for Spring XD install while specifying redis as dependency.  - starting up stream server upon successful brew install  couple of questions: - should we name the brew task springxd? (name not taken yet) - should we start the stream server as part of the brew install process? - should we specify redis as a recommended dependency? user can pass in 'brew install springxd --without-redis' to skip redis installation. by default, 'brew install springxd' will install redis as well."
Answer: 8305.0

User story: "Update a gemfire region."
Answer: 10071.0

User story: "Do not require a POJO in order to do end-to-end processing in a batch step."
Answer: 10114.0