[ 
https://issues.apache.org/jira/browse/ASTERIXDB-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15534686#comment-15534686
 ] 

ASF subversion and git services commented on ASTERIXDB-1636:
------------------------------------------------------------

Commit 2685b60d9e03a515fcc5260a3dd4399740f5ec40 in asterixdb's branch 
refs/heads/master from [~imaxon]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=2685b60 ]

Fixes for ASTERIXDB-1636

The index of the tuple field for filters from SecondaryIndexOperationsHelper 
and AqlMetadataProvider
differed. The one in AqlMetadataProvider was wrong, as it was attempting to 
take into account the
presence of a partitioning field in the incoming tuple, which is not there in 
the case of an
insert/upsert.

There was also an issue where on merge, for components with a filter page but 
no min/max, the merge
would fail. I fixed this by skipping over null entries while getting the 
min/max of merging components.

Finally, there was a very silly error in LSMComponentFilterManager which was 
causing the filter page
to appear as blank, because the page was being pinned with the wrong argument. 
That is also fixed.

Change-Id: Ib4bc413fcda9a5c98ae57f94e1c8a68fe9aacda3
Reviewed-on: https://asterix-gerrit.ics.uci.edu/1205
Sonar-Qube: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Reviewed-by: Taewoo Kim <wangs...@yahoo.com>
Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <jenk...@fulliautomatix.ics.uci.edu>


> Feed cannot re-ingest after cluster restart
> -------------------------------------------
>
>                 Key: ASTERIXDB-1636
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1636
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: Feeds, Storage
>         Environment: master
> commit c89d668f68e5430a6ba4455daf8f9cd6f7040dd8
> Date:   Tue Sep 6 18:29:23 2016 -0700
>            Reporter: Jianfeng Jia
>            Assignee: Ian Maxon
>            Priority: Blocker
>              Labels: soon
>
> Here are steps to reproduce the problem:
> 1. start the cluster
> 2. ingest the initial data using file feed 
> [script|https://gist.github.com/JavierJia/9ed7744c938c5cb66aba63007b86a987]
> 2.1: file for ingestion: 
> https://drive.google.com/open?id=0B423M7wGZj9dNE5HenFqcjhuUFk
> 3. start another socket feed 
> [script|https://gist.github.com/JavierJia/565cefd9322df35c7abeefbfcfcee9f8] 
> to ingest the live data  
> 4. restart the cluster
> 5. start that live socket feed again.
> 6. with your own twitter credential you can use [this 
> script|https://github.com/ISG-ICS/cloudberry/blob/master/streamFeed.sh]  to 
> ingest the tweet
> 7. It will send at most 280 tweets and stops forever.
> [~imaxon] [~idleft] if you can help that will be great.
> related to ASTERIXDB-1264



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to