Clone Tools
Constraints: committers
Constraints: files
Constraints: dates
Rename test to tests/phx

  1. … 77 more files in changeset.
Move win-odbc64 into subdir to combine repos

  1. … 554 more files in changeset.
Merge remote branch 'win-odbc64/stable/1.1' into stable/1.1

Move phoenix_test into test subdir to combine repos

  1. … 78 more files in changeset.
Merge remote branch 'phoenix_test/stable/1.1' into stable/1.1

Move dcs into subdir to combine repos

  1. … 560 more files in changeset.
Merge remote branch 'dcs/stable/1.1' into stable/1.1

Move core into subdir to combine repos

    • -573
    • +0
  1. … 10754 more files in changeset.
Changed the HDP repository location to pick the latest one

Change-Id: Iae13212c6c082b0602477afa8f2b2fe1bffcd318

    • -1
    • +1
Partial fix for bug 1449343 and fixes driver core with pyODBC

Fixes issue where the last few bytes of data are lost for nullable columns that

are greater than 32K. This also fixes a core seen on the ODBC driver

side from a query run by HPDSM via pyODBC.

Partially fixes 1449343

Change-Id: I61c1f5a00ffd7da54467e3be288433045fa2951b

Fix for bug 1446802

This is a fix on ODBC driver side specifically

against MXOSRVR recent change by bug 1438775

Change-Id: Id1dff8f45a9e121149781ba2a84c983f9265b90f

(cherry picked from commit ca56ccb5b3c054a6ceb042b1d43faacb9564052b)

LP 1446802: ODBC SQLFetch fails when column size is bigger than 64K

Change-Id: Iaa125e18c40bc5953f646740d12ba3b9bbf1c5fb

Merge "Change default review branch for stable/1.1" into stable/1.1

Fix for bug 1446043

SPJ's can contain duplicate column names coming from different tables

which will be resolved later by renaming the columns. so there is no

need to check for duplicates at the beginning of bind node for SPJ's.

Change-Id: I28146c698bae7622e27b326ab0411e9a3ef56c2c

Expected file change for failing hive test.

A previous checkin that enhanced an error message and caused this diff. So

just had to update the expected file.

Change-Id: I1cc5133e7bf971b98fc6e79f7cad05553eed6b46

(cherry picked from commit 233d4ca7bf16d5bb629be069e87a2f06e5956c02)

Delay added to TransactionManager call retries, LP 1439387

Change-Id: Iccaf80cb787661c95648c37fbb31b6e7f4d8badb

Change default review branch for stable/1.1

Change-Id: Ia83ac3e88b185e2b3e9193d4432b587e2c293c01

Merge "Fix for bug 1437102"

Merge "Fix for bug 1438775"

Fix for bug 1437102

Recently we turned off fast path IPC processiong for T2 to fix an other bug. With that we are exectuing non fast path code which was not being used for a long time even in SQ. As some changes were made to IPC layer, changes to this path were missed. So any ESP plan in T2 is hanging in non fast path because we are using BAWAITIOX instead of thread specific BAWAITIOXTS. This was not caught because none of T2 tests have any ESP plan queries.

Change-Id: Ie1e59d108fe6b49656407885bbabca2d1ebc60f6

Fix for bug 1438775

The fetch buffer size calculation did not account for varchar indicator

length for columns greater than 32K. The indicator length in this case is 4 bytes instead of 2. Currently, the buffer length calculation was using 2, which resulted in allocating insufficient memory leading to a corruption.

Fixes bug 1438775

Change-Id: Ib16b6644ca3c7f36d96687a33ea36ad4f0ffe903

Fix for bug 1443688

Explain plan is now collected only for non-unique query types and queries that generate stats.

Also, fixed a bug where explain plan was being collected even though the

statistics feature is disabled.

Fixes bug 1443688

Change-Id: I67433083758044e1da0071241e00c4a09e701dbd

    • -0
    • +11
Merge "Support for TM not running state - output for REST/HPDSM"

Merge "Fix LP Bug 1382686 - LIKE predicate fails on some UTF8 columns"

Merge "[bug:1440941]T2 Phoenix tests creating cores at CliStatement::doOltExecute"

    • -0
    • +6
Support for TM not running state - output for REST/HPDSM

Added a new state for dtmci to handle all error situations when

a response is not received by the TM. So far, these errors are

handled as a NOT RUNNING state for the TM. Display in json format

has been corrected.

Change-Id: Id19c73a47ad4ae49dac231962e1d3d5e8ae96dc0

Merge "Fixes in T2 driver to enable OE performance run"

Fix LP Bug 1382686 - LIKE predicate fails on some UTF8 columns

The description of this LP bug says that the LIKE predicate fails when

the pattern string starts with a '%' and when selecting from a view, but

not when selecting from the underlying table. However, in the supplied

reproducible test case, the view's column had a character set of UTF8

while the underlying table had a character set of UCS2.

As it turns out, the real problem is not related to selecting from a

view. The root cause is a bug in the PCODE implementation for the LIKE

predicate and this problem can occur any time the LIKE predicate is

applied to a column declared as VARCHAR(nnn) CHARACTER SET UTF8 where

128 <= nnn <= 255... and the problem may not be limited to situations

where the LIKE pattern starts with a '%'.

When nnn > 255, the PCODE implmentation is not used, so the problem does

not occur then.

The root cause is a place in the code where the length of the column (in

characters, not bytes) is stored in a single byte and is retrieved as if

that byte contains a *signed* value. When 128 <= nnn <= 255, that

retrieval results in a negative value. The fix is to retrieve the value

as an *unsigned* value.

NOTE: This commit changes 2 lines of code. The second line changed is

the only one necessary to fix the problem. The first line is being

changed as well because it has a similar problem and would prevent the

LIKE predicate from working properly if the LIKE pattern had more than

127 pattern parts.

Change-Id: Ideb063cbd62b9155e9b1f579bcd0edb187e8a1c8

Merge "Updated known diff file for compGeneral/TEST006"

[bug:1440941]T2 Phoenix tests creating cores at CliStatement::doOltExecute

Change-Id: I31d42e96bf15ebd58ca9bd2f9a2532030d0f0e02

    • -0
    • +6