Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-1394

kafka avro adapter install avro library issues

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 1.1.4
    • 1.1.5
    • None
    • None
    • 2018-10, 2018-11, 2018-12

    Description

      yum localinstall mariadb-columnstore-kafka-avro-adapters-1.1.4-1-x86_64-centos7.rpm
      Loaded plugins: fastestmirror
      Examining mariadb-columnstore-kafka-avro-adapters-1.1.4-1-x86_64-centos7.rpm: mariadb-columnstore-kafka-avro-adapters-1.1.4-1.x86_64
      Marking mariadb-columnstore-kafka-avro-adapters-1.1.4-1-x86_64-centos7.rpm to be installed
      Resolving Dependencies
      --> Running transaction check
      ---> Package mariadb-columnstore-kafka-avro-adapters.x86_64 0:1.1.4-1 will be installed
      --> Processing Dependency: libavro.so.23.0.0()(64bit) for package: mariadb-columnstore-kafka-avro-adapters-1.1.4-1.x86_64
      Loading mirror speeds from cached hostfile

      • base: centos.mirrors.tds.net
      • epel: mirrors.lug.mtu.edu
      • extras: mirror.steadfast.net
      • updates: mirrordenver.fdcservers.net
        --> Finished Dependency Resolution
        Error: Package: mariadb-columnstore-kafka-avro-adapters-1.1.4-1.x86_64 (/mariadb-columnstore-kafka-avro-adapters-1.1.4-1-x86_64-centos7)
        Requires: libavro.so.23.0.0()(64bit)
        You could try using --skip-broken to work around the problem
        You could try running: rpm -Va --nofiles --nodigest

      Attachments

        Activity

          People

            dthompson David Thompson (Inactive)
            dthompson David Thompson (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.