1. 01 10月, 2021 1 次提交
  2. 28 9月, 2021 3 次提交
  3. 27 9月, 2021 2 次提交
  4. 09 9月, 2021 1 次提交
  5. 06 9月, 2021 2 次提交
  6. 03 9月, 2021 1 次提交
  7. 01 9月, 2021 1 次提交
  8. 27 8月, 2021 1 次提交
  9. 18 8月, 2021 1 次提交
  10. 15 8月, 2021 1 次提交
  11. 14 8月, 2021 1 次提交
    • W
      fix: Fix MultiScopesAnalysisListener#setPublicAttrs log warn frequently (#7271) · 4b66f1e0
      wallezhang 提交于
      * fix: Fix MultiScopesAnalysisListener#setPublicAttrs log warn frequently. #6562
      
      1. Rename current STATUS_CODE to HTTP_RESPONSE_STATUS_CODE, real tag key should be http.status_code.
      2. Add a new string tag RPC_RESPONSE_STATUS_CODE to hold all string type value tag. The key is `rpc.status_code`.
      3. At the backend, keep responseCode for HTTP_RESPONSE_STATUS_CODE tag, but add @Deprecated. Also, add httpResponseStatusCode(a duplicate of responseCode) and rpcStatusCode(for RPC_RESPONSE_STATUS_CODE) fields for OAL.
      
      * Modify `Tags.STATUS_CODE` field name to `Tags.HTTP_RESPONSE_STATUS_CODE` and type from `StringTag` to `IntegerTag`, add `Tags.RPC_RESPONSE_STATUS_CODE` field to hold rpc response code value.
      
      * Add `rpcStatusCode` for `rpc.status_code` tag in the OAL objects. The `responseCode` field is marked as deprecated and replaced by `httpResponseStatusCode` field. 
      
      * Tag `status_code` is still supported in the backend for forward compatbility. Will be removed one year later.
      Co-authored-by: wu-sheng's avatar吴晟 Wu Sheng <wu.sheng@foxmail.com>
      4b66f1e0
  12. 12 8月, 2021 1 次提交
  13. 10 8月, 2021 1 次提交
  14. 06 8月, 2021 2 次提交
  15. 02 8月, 2021 1 次提交
  16. 25 7月, 2021 1 次提交
  17. 22 7月, 2021 1 次提交
  18. 18 7月, 2021 1 次提交
    • wuweijie@apache.org's avatar
      Remove plugins for ShardingSphere legacy and unstable versions (#7323) · 06e589fa
      wuweijie@apache.org 提交于
      Remove the following plugins due to they are legacy and unstable releases.
      1. sharding-jdbc-1.5.x-plugin
      2. sharding-sphere-4.x-rc3-plugin
      3. sharding-sphere-4.x-plugin (This is for RC1 and RC2)
      
      To people who want to use these removing versions, you still could copy the plugins from SkyWalking's 8.6.0 release to the '/plugins' folder to activate, unless SkyWalking has some core level APIs upgrade. This is very rare to happen.
      06e589fa
  19. 16 7月, 2021 1 次提交
  20. 14 7月, 2021 2 次提交
    • F
      feat: update e2e for client-js (#7297) · ff7c8fa8
      Fine0830 提交于
      ff7c8fa8
    • wu-sheng's avatar
      Remove synchronous persistence mechanism in API level and ElasticSearch implementation (#7293) · de975c7e
      wu-sheng 提交于
      * Performance: remove the synchronous persistence mechanism from batch ElasticSearch DAO. Because the current enhanced persistent session mechanism, don't require the data queryable immediately after the insert and update anymore.
      * Performance: share `flushInterval` setting for both metrics and record data, due to `synchronous persistence mechanism` removed. Record flush interval used to be hardcoded as 10s.
      * Remove `syncBulkActions` in ElasticSearch storage option.
      * Increase the default bulkActions(env, SW_STORAGE_ES_BULK_ACTIONS) to 5000(from 1000).
      * Increase the flush interval of ElasticSearch indices to 15s(from 10s)
      
      Add these 2 references. According to these, **(same _index, _type and _id) in same bulk will be in order**
      1. https://github.com/elastic/elasticsearch/issues/50199
      2. https://discuss.elastic.co/t/order-of--bulk-request-operations/98124
      
      Notice, the order of different bulks is not guaranteed by the ElasticSearch cluster. We are going to have the risk of dirty write. But consider we set over 20s period between flush, and index flush period is 10, we should be safe.
      
      Recommend 5000 bulk size and 15s flush interval only. The persistent period has been set to 25s.
      de975c7e
  21. 09 7月, 2021 2 次提交
  22. 08 7月, 2021 2 次提交
  23. 07 7月, 2021 2 次提交
  24. 04 7月, 2021 1 次提交
  25. 03 7月, 2021 2 次提交
  26. 02 7月, 2021 1 次提交
  27. 30 6月, 2021 2 次提交
  28. 28 6月, 2021 1 次提交
  29. 22 6月, 2021 1 次提交