GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — error: "Snowflake Data Type is not supported" on "NUMBER" with non-zero scale · Issue #3146 · feast-dev/feast

error: "Snowflake Data Type is not supported" on "NUMBER" with non-zero scale #3146

New issue
Copy link
New issue
Copy link
Closed
#3148
Closed
error: "Snowflake Data Type is not supported" on "NUMBER" with non-zero scale#3146
#3148
Copy link
Labels
kind/bugpriority/p2

Description

@cburroughs
cburroughs
opened on Aug 26, 2022
Issue body actions

Expected Behavior

feast plan/apply completed without error in version 0.23.0 and I was able to query with get_historical_features.

Current Behavior

With the snowflake datatype NUMBER(38,6) I get:

NotImplementedError: The following Snowflake Data Type is not supported: DECIMAL -- Convert to DOUBLE

Steps to reproduce

  • $ feast init -t snowflake
  • Alter the table like so:
alter table SNOWY_FEAST.PUBLIC."amazed_dane_feast_driver_hourly_stats" add column temp_conv_rate NUMBER(38,6);
update SNOWY_FEAST.PUBLIC."amazed_dane_feast_driver_hourly_stats" set temp_conv_rate = "conv_rate";
alter table SNOWY_FEAST.PUBLIC."amazed_dane_feast_driver_hourly_stats" drop column "conv_rate";
alter table SNOWY_FEAST.PUBLIC."amazed_dane_feast_driver_hourly_stats" rename column temp_conv_rate to "conv_rate";
  • $ feast apply
Traceback (most recent call last):
...
   raise NotImplementedError(
NotImplementedError: The following Snowflake Data Type is not supported: DECIMAL -- Convert to DOUBLE

Specifications

  • Version: Feast SDK Version: "feast 0.24.0"
  • Platform: x86_64 on Python 3.10.5
  • Subsystem: Linux 5.4.203-

Possible Solution

Activity

  1. cburroughs
    added
    kind/bug
    priority/p2
    on Aug 26, 2022
  2. achals commented on Aug 26, 2022

    @achals
    achals
    on Aug 26, 2022
    Member
    More actions

    I think this is intentional cc @sfc-gh-madkins

  3. sfc-gh-madkins commented on Aug 27, 2022

    @sfc-gh-madkins
    sfc-gh-madkins
    on Aug 27, 2022
    Collaborator
    More actions

    @cburroughs my advice for right now would be to cast this to type double/float, as the error recommends. Let me see if I can get NUMBER with scale to work.

    The issue stems from afew things. One protobuf doesnt support fixed point numbers, with scale. Two, how NUMBER is passed to pandas types.

  4. feast-ci-bot
    closed this as completedin #3148on Aug 29, 2022
  5. cburroughs commented on Aug 30, 2022

    @cburroughs
    cburroughs
    on Aug 30, 2022
    ContributorAuthor
    More actions

    I installed from master to test it out. Looks good; thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugpriority/p2

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.