Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

copr: Vectorize AddDatetimeAndString #9610

Merged
merged 2 commits into from
Feb 2, 2021

Conversation

weastel
Copy link
Contributor

@weastel weastel commented Jan 31, 2021

Signed-off-by: Drumil Patel drumilpatel720@gmail.com

What problem does this PR solve?

Issue Number: Partially fixes #9016

Problem Summary: Added Vectorize version for AddDatetimeAndString

What is changed and how it works?

What's Changed: Implmented Vectorize vesion for AddDatetimeAndString

Check List

Tests

  • Unit test

Release note

Signed-off-by: Drumil Patel <drumilpatel720@gmail.com>
@ti-srebot ti-srebot added the first-time-contributor Indicates that the PR was contributed by an external member and is a first-time contributor. label Jan 31, 2021
@ti-chi-bot
Copy link
Member

Welcome @weastel!

It looks like this is your first PR to tikv/tikv 🎉.

I'm the bot to help you request reviewers, add labels and more, See available commands.

We want to make sure your contribution gets all the attention it needs!



Thank you, and welcome to tikv/tikv. 😃

@ti-chi-bot ti-chi-bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jan 31, 2021
@zhongzc
Copy link
Contributor

zhongzc commented Feb 1, 2021

/cc @Xuanwo @andylokandy

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Feb 2, 2021
Copy link
Contributor

@andylokandy andylokandy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@ti-chi-bot
Copy link
Member

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • Xuanwo
  • andylokandy

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

@ti-chi-bot ti-chi-bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Feb 2, 2021
@ti-chi-bot ti-chi-bot requested a review from Xuanwo February 2, 2021 06:10
@andylokandy
Copy link
Contributor

/merge

@ti-chi-bot
Copy link
Member

@andylokandy: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

@ti-chi-bot
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: 6c8059d

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Feb 2, 2021
@ti-chi-bot
Copy link
Member

@weastel: Your PR has out-of-dated, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

@Xuanwo
Copy link
Member

Xuanwo commented Feb 2, 2021

Please don't use fixes #9016 in issue, or #9016 will be closed.

@ti-chi-bot ti-chi-bot merged commit 74809fa into tikv:master Feb 2, 2021
Little-Wallace added a commit to Little-Wallace/tikv that referenced this pull request Feb 4, 2021
commit 74809fa
Author: Drumil Patel <42701709+weastel@users.noreply.github.com>
Date:   Tue Feb 2 11:57:45 2021 +0530

    copr: Vectorize AddDatetimeAndString (tikv#9610)

    Signed-off-by: Drumil Patel <drumilpatel720@gmail.com>

    <!--
    Thank you for contributing to TiKV!

    If you haven't already, please read TiKV's [CONTRIBUTING](https://github.com/tikv/tikv/blob/master/CONTRIBUTING.md) document.

    If you're unsure about anything, just ask; somebody should be along to answer within a day or two.

    PR Title Format:
    1. module [, module2, module3]: what's changed
    2. *: what's changed

    If you want to open the **Challenge Program** pull request, please use the following template:
    https://raw.githubusercontent.com/tikv/.github/master/.github/PULL_REQUEST_TEMPLATE/challenge-program.md
    You can use it with query parameters: https://github.com/tikv/tikv/compare/master...${you branch}?template=challenge-program.md
    -->

    ### What problem does this PR solve?

    Issue Number: Partially fixes tikv#9016 <!-- REMOVE this line if no issue to close -->

    Problem Summary: Added Vectorize version for AddDatetimeAndString

    ### What is changed and how it works?

    What's Changed: Implmented Vectorize vesion for AddDatetimeAndString

    ### Check List <!--REMOVE the items that are not applicable-->

    Tests <!-- At least one of them must be included. -->

    - Unit test

    ### Release note <!-- bugfixes or new feature need a release note -->
    - Partially fixes tikv#9016

commit 103f5ff
Author: Xintao <hunterlxt@live.com>
Date:   Tue Feb 2 13:13:45 2021 +0800

    Make TiKV not to create dict files when master_key cannot work (tikv#9540)

    Signed-off-by: Xintao <hunterlxt@live.com>

    <!--
    Thank you for contributing to TiKV!

    If you haven't already, please read TiKV's [CONTRIBUTING](https://github.com/tikv/tikv/blob/master/CONTRIBUTING.md) document.

    If you're unsure about anything, just ask; somebody should be along to answer within a day or two.

    PR Title Format:
    1. module [, module2, module3]: what's changed
    2. *: what's changed

    If you want to open the **Challenge Program** pull request, please use the following template:
    https://raw.githubusercontent.com/tikv/.github/master/.github/PULL_REQUEST_TEMPLATE/challenge-program.md
    You can use it with query parameters: https://github.com/tikv/tikv/compare/master...${you branch}?template=challenge-program.md
    -->

    ### What problem does this PR solve?

    Issue Number: close tikv#9488

    Problem Summary:
    At the first time TiKV access AWS KMS failed, it leaves corrupted dict file which causes TiKV to crash continuously.

    ### What is changed and how it works?

    check the `master_key` before creating the dicts.

    ### Related changes

    - PR to update `pingcap/docs`/`pingcap/docs-cn`:
    - PR to update `pingcap/tidb-ansible`:
    - Need to cherry-pick to the release branch

    ### Check List <!--REMOVE the items that are not applicable-->

    Tests <!-- At least one of them must be included. -->

    - Unit test
    - Integration test
    - Manual test (add detailed scripts or steps below)
    - No code

    Side effects

    - Performance regression
        - Consumes more CPU
        - Consumes more MEM
    - Breaking backward compatibility

    ### Release note <!-- bugfixes or new feature need a release note -->
    - Fix the bug that TiKV could not start normally after failing to access AWS KMS.

commit af4432f
Author: Wallace <bupt2013211450@gmail.com>
Date:   Tue Feb 2 11:49:45 2021 +0800

    importer: fix test_ingest_sst (tikv#9617)

    Signed-off-by: Little-Wallace <bupt2013211450@gmail.com>

    <!--
    Thank you for contributing to TiKV!

    If you haven't already, please read TiKV's [CONTRIBUTING](https://github.com/tikv/tikv/blob/master/CONTRIBUTING.md) document.

    If you're unsure about anything, just ask; somebody should be along to answer within a day or two.

    PR Title Format:
    1. module [, module2, module3]: what's changed
    2. *: what's changed

    If you want to open the **Challenge Program** pull request, please use the following template:
    https://raw.githubusercontent.com/tikv/.github/master/.github/PULL_REQUEST_TEMPLATE/challenge-program.md
    You can use it with query parameters: https://github.com/tikv/tikv/compare/master...${you branch}?template=challenge-program.md
    -->

    ### What problem does this PR solve?

    Issue Number: close tikv#9472

    Problem Summary:
    TiKV may cleanup sst which has been upload just, so the ingest-job will success because it can not found file in path before it starts proposing, and the error is checked only when applied this entries.

    ### What is changed and how it works?

    We do not need to check and cleanup sst very quickly in this tests, so I remove the configuration for `cleanup_import_sst_interval`.

    ### Related changes

    - PR to update `pingcap/docs`/`pingcap/docs-cn`:
    - PR to update `pingcap/tidb-ansible`:
    - Need to cherry-pick to the release branch

    ### Check List <!--REMOVE the items that are not applicable-->

    Tests <!-- At least one of them must be included. -->

    - Unit test
    - Integration test
    - Manual test (add detailed scripts or steps below)
    - No code

    Side effects

    - Performance regression
        - Consumes more CPU
        - Consumes more MEM
    - Breaking backward compatibility

    ### Release note <!-- bugfixes or new feature need a release note -->

    - No release note.

commit 80582cb
Author: wangggong <793160615@qq.com>
Date:   Mon Feb 1 13:15:45 2021 +0800

    copr: Implement regexp & regexp_utf8 (tikv#9238)

    Signed-off-by: wangggong <793160615@qq.com>

    <!--
    Thank you for contributing to TiKV!

    If you haven't already, please read TiKV's [CONTRIBUTING](https://github.com/tikv/tikv/blob/master/CONTRIBUTING.md) document.

    If you're unsure about anything, just ask; somebody should be along to answer within a day or two.

    PR Title Format:
    1. module [, module2, module3]: what's changed
    2. *: what's changed

    If you want to open the **Challenge Program** pull request, please use the following template:
    https://raw.githubusercontent.com/tikv/.github/master/.github/PULL_REQUEST_TEMPLATE/challenge-program.md
    You can use it with query parameters: https://github.com/tikv/tikv/compare/master...${you branch}?template=challenge-program.md
    -->

    ### What problem does this PR solve?

    Issue Number: tikv#9016

    Problem Summary:

    ### What is changed and how it works?

    What's Changed:

    Add regexp & regexp_utf8

    ### Related changes

    ### Check List <!--REMOVE the items that are not applicable-->

    Tests <!-- At least one of them must be included. -->

    - Unit test

    Side effects

    ### Release note <!-- bugfixes or new feature need a release note -->

    No release note.

commit 7b260d1
Author: Jay <BusyJay@users.noreply.github.com>
Date:   Fri Jan 29 21:13:44 2021 +0800

    resolve: detect tombstone correctly (tikv#9593)

    <!--
    Thank you for contributing to TiKV!

    If you haven't already, please read TiKV's [CONTRIBUTING](https://github.com/tikv/tikv/blob/master/CONTRIBUTING.md) document.

    If you're unsure about anything, just ask; somebody should be along to answer within a day or two.

    PR Title Format:
    1. module [, module2, module3]: what's changed
    2. *: what's changed

    If you want to open the **Challenge Program** pull request, please use the following template:
    https://raw.githubusercontent.com/tikv/.github/master/.github/PULL_REQUEST_TEMPLATE/challenge-program.md
    You can use it with query parameters: https://github.com/tikv/tikv/compare/master...${you branch}?template=challenge-program.md
    -->

    ### What problem does this PR solve?

    Issue Number: close tikv#9590

    Problem Summary:

    PD client filter tombstone store and return error instead. Resolver should recognize the error and handle it correctly.

    ### Check List <!--REMOVE the items that are not applicable-->

    Tests <!-- At least one of them must be included. -->

    - Unit test
    - Integration test

    ### Release note <!-- bugfixes or new feature need a release note -->
    - Fix repeated tombstone logs when sunset nodes

commit a2c7aac
Author: Liqi Geng <gengliqiii@gmail.com>
Date:   Fri Jan 29 04:03:44 2021 -0600

    raftstore: enlarge leader-transfer-max-log-lag (tikv#9592)

    Signed-off-by: gengliqi <gengliqiii@gmail.com>

    ### What problem does this PR solve?

    Problem Summary:
    The meaning of `leader-transfer-max-log-lag` has already been changed by tikv#6539.
    For now, it means the difference value between the leader's last log index and the follower's last applied index.
    On the basis of implementation, we get the follower's last applied index through an RPC then we get the leader's last log index.
    There are many gaps between this process.
    1. the applied index in peer fsm may be smaller than the real one in its corresponding apply fsm
    2. the network latency
    3. some logs may be proposed after sending the query RPC to this follower

    So the follower's last applied index may be much larger when we calculate the difference value.

    It thus appears that the default value of `leader-transfer-max-log-lag`(10) is too small which leads to many failures of leader transfer.

    I test the value of 128 and the failure is much less than before.
    * I test 256 and there is almost no failure. But maybe it's too large.

    Maybe we should find a more scientific approach to solve this problem later.

    ### What is changed and how it works?

    What's Changed:
    Change the default value of `leader-transfer-max-log-lag` to 128.

    ### Related changes

    - PR to update `pingcap/docs`/`pingcap/docs-cn`:
    - PR to update `pingcap/tidb-ansible`:
    - Need to cherry-pick to the release branch

    Tests <!-- At least one of them must be included. -->

    - No code

    Side effects

    - No

    ### Release note <!-- bugfixes or new feature need a release note -->
    * Change the default `leader-transfer-max-log-lag` to 128 to increase the success rate of leader transfer

commit 3a4b8bb
Author: Greg Weber <greg@pingcap.com>
Date:   Thu Jan 28 20:41:44 2021 -0600

    fix: broken build on Mac (tikv#9598)

    On Mac:

    ```
     --> components/file_system/src/rate_limiter.rs:5:5
    5 | use crossbeam_utils::CachePadded;
      |     ^^^^^^^^^^^^^^^ use of undeclared crate or module `crossbeam_utils`
    ```

    ### Release note

    * None

commit 20b0e95
Author: Xinye Tao <xy.tao@outlook.com>
Date:   Thu Jan 28 18:05:43 2021 +0800

    engine: refactor `MetricsFlusher` and add fallback storage IO measuring (tikv#9458)

    Signed-off-by: tabokie <xy.tao@outlook.com>

    ### What is changed and how it works?

    What's Changed:

    Remove metrics flusher in engine_traits and use background worker instead, add IO metrics task which reports statistics from iosnooper, or IO rate limiter if BCC is unavailable.

    ### Check List <!--REMOVE the items that are not applicable-->

    Tests <!-- At least one of them must be included. -->

    - Unit test

    ### Release note <!-- bugfixes or new feature need a release note -->

    No release note

Signed-off-by: Little-Wallace <bupt2013211450@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
first-time-contributor Indicates that the PR was contributed by an external member and is a first-time contributor. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Coprocessor functions migration from non-vec framework
6 participants