merge with apache - #3
Merged
Merged
Conversation
* restore accidently deleted display complex datatypes code * added javadoc
This reverts commit ec536e1. PR 1116 included some issues, which will be fixed in PR 1117: 1) semantic change to return values of IncomingMessageEnvelope.getEventTime and IncomingMessageEnvelope.getArrivalTime (changed from millis to nanos) which are public API methods, and it will be hard to find existing usages to make sure they are updated properly, 2) usages of constructor of IncomingMessageEnvelope was not updated to handle nanos correctly in certain places (e.g. KafkaConsumerProxy)
…ot reflected in code In the current code, the window is only applied and checked on the last retry. However, the check should be done at all retries. This was found during #1104 rmatharu please take a look Author: Daniel Nishimura <dnishimura@gmail.com> Reviewers: Ray Matharu <rmatharu@linkedin.com> Closes #1108 from dnishimura/samza-2277-cluster-manager-retry-window-bug-fix and squashes the following commits: 23db835 [Daniel Nishimura] Address minor comments from @rmatharu 0a7c927 [Daniel Nishimura] Trigger build b/c of flakey test. 0c56499 [Daniel Nishimura] Fix checkstyle 2674f75 [Daniel Nishimura] Address @rmatharu's comments. ecfe63e [Daniel Nishimura] SAMZA-2277: Semantics for cluster-manager.container.retry.window.ms not reflected in code
Add a putsAll API to the metadata store API. This allows for a delayed flush() call for underlying stores that require a flush() after write such as Kafka. Author: Daniel Nishimura <dnishimura@gmail.com> Reviewers: mynameborat <bharath.kumarasubramanian@gmail.com> Closes #1112 from dnishimura/samza-2276-metadata-store-putall-api and squashes the following commits: 830b599 [Daniel Nishimura] Update javadoc for MetadataStore#putAll e52d884 [Daniel Nishimura] SAMZA-2271: Add Metdata store putAll API
…m SamzaContainer startup sequence. (#1119)
…in changelog (#1008) * Throw a record too large exception for changelog oversized records * Change implementation to handle large messages in CachedStore based on user defined configs * Address review and change new Scala classes to Java * Address review and add a test case
…ContainerRunner (#1120)
…ment (#1121) * Removing RegEx while parsing the sql statement * Adding few more parser tests * Adding verbose logging
* Samza-sql: Fix udf to work with disabled arg check. * Samza-sql: Fix udf to work with disabled arg check. * Samza-sql: Fix udf to work with disabled arg check.
…ch even if offsets are correctly set (#1127) * SAMZA-2291: Custom IME Put in TestRunner runs into Offset mismatch even on correct offsets * Addressing comments
Adding two additional params to DiagnosticsStreamMessage
…ectly Author: mynameborat <bharath.kumarasubramanian@gmail.com> Reviewers: xinyuiscool <xiliu@linkedin.com> Closes #1129 from mynameborat/async-watermark-propagation-fix
…ation test harnesses to improve test run times (#1128)
(messages-behind-high-watermark and high-watermark) are calculated from kafka's "records-lag" consumer metric. In version 1.1 or so, when metrics moved from including the topic name in the metric name to using tags, they added a replacement of period to underscore. See commit : apache/kafka@5d81639#diff-b45245913eaae46aa847d2615d62cde0R1331
SAMZA-2295 : records-lag based topic metrics not working for topics with periods (dot, '.') in them
* SAMZA-2296: Metadata streams not created in Standalone * Trigger
… only once Author: mynameborat <bharath.kumarasubramanian@gmail.com> Reviewers: Aditya Toomula <atoomula@linkedin.com> Closes #1135 from mynameborat/SAMZA-2299 and squashes the following commits: 81cc51a [mynameborat] Address Dengpan's comments 41a9165 [mynameborat] SAMZA-2299: StreamTableJoin operator should invoke user join function only once
…host-affinity allocations (#1104) * SAMZA-2266: Introduce a backoff when there are repeated failures for host-affinity allocations
…lding job model (#1141)
This fixes two broken links in deployment model page (to YARN and standalone deployment pages).
Fixed broken links in documentation
…m DiagnosticsManager (#1145) * Emitting numPersistentStores instead of num stores with changelog
* Adding validation for Samza Sql statements. * Adding validation for Samza Sql statements. * Adding validation for Samza Sql statements. * Adding validation for Samza Sql statements. * Adding validation for Samza Sql statements. * Adding validation for Samza Sql statements.
…or processing time and query latency (#1117)
…ma are set in the projected fields. (#1149) * Validate that all non-default value fields in output schema are set in the projected fields. * Added comments and renamed sqlFieldSchema member variables.
…removed (#1150) In the previous PR: https://github.com/apache/samza/pull/1010/files config with null/empty values will be filter out when reading the coordinator stream, this will cause some problems when the user expects an empty string to be a value config.
* Fix discrepancy between sql REAL and FLOAT
The fix removes the need to join on the main thread which causes a deadlock when a signal is recieved.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
14 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.