Skip to content

Add Date32, Datetime64, Timestamp64, Interval64 to supported for DqMergeCh #30305

@dahbka-lis

Description

@dahbka-lis

There is a function for type validations with unsupported ext date types:

bool IsTypeSupportedInMergeCn(EDataSlot type) {
    switch (type) {
        case EDataSlot::Bool:
        case EDataSlot::Int8:
        case EDataSlot::Uint8:
        case EDataSlot::Int16:
        case EDataSlot::Uint16:
        case EDataSlot::Int32:
        case EDataSlot::Uint32:
        case EDataSlot::Int64:
        case EDataSlot::Uint64:
        case EDataSlot::Double:
        case EDataSlot::Float:
        case EDataSlot::String:
        case EDataSlot::Utf8:
        case EDataSlot::Uuid:
        case EDataSlot::Date:
        case EDataSlot::Datetime:
        case EDataSlot::Timestamp:
        case EDataSlot::Interval:
        case EDataSlot::Decimal:
        case EDataSlot::DyNumber:
            // Supported
            return true;
        case EDataSlot::Yson:
        case EDataSlot::Json:
        case EDataSlot::TzDate:
        case EDataSlot::TzDatetime:
        case EDataSlot::TzTimestamp:
        case EDataSlot::JsonDocument:
        case EDataSlot::Date32:
        case EDataSlot::Datetime64:
        case EDataSlot::Timestamp64:
        case EDataSlot::Interval64:
        case EDataSlot::TzDate32:
        case EDataSlot::TzDatetime64:
        case EDataSlot::TzTimestamp64:
            return false;
    }
    return false;
}

But DqMergeCh supports ext date types, so need to move types to Supported and check that SELECT ... FROM ... ORDER BY Date32 works fine

Metadata

Metadata

Assignees

Labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions